Small step to prepare for native node glob support, and test waters of dep hygiene #176
Pull Request #176 Alerts: Success
| Report | Status | Message |
|---|---|---|
| PR #176 Alerts | ✅ | No new dependency alerts |
Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.
Details
👍 No dependency issues detected. Learn more about Socket for GitHub ↗︎
No security issues detected in this pull request.
Ignoring: npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@esbuild/[email protected], npm/@jdalton/[email protected], npm/@mdn/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@nolyfill/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]
Next steps
Take a deeper look at the dependency
Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.
Remove the package
If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.
Mark a package as acceptable risk
To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all