test: attribution bot 2 #24868
test: attribution bot 2 #24868
Pull Request #24868 Alerts: Complete with warnings
| Report | Status | Message |
|---|---|---|
| PR #24868 Alerts | Found 10 project alerts |
Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.
Details
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
| Alert | Package | Note | Source |
|---|---|---|---|
| New author | npm/@npmcli/fs@2.1.2 |
| |
| Deprecated | npm/@npmcli/move-file@2.0.1 |
| |
| New author | npm/are-we-there-yet@3.0.1 |
|
|
| Network access | npm/make-fetch-happen@10.2.1 |
| |
| Network access | npm/make-fetch-happen@10.2.1 |
| |
| Network access | npm/make-fetch-happen@10.2.1 |
| |
| Network access | npm/make-fetch-happen@10.2.1 |
| |
| New author | npm/nopt@6.0.0 | ||
| New author | npm/npmlog@6.0.2 |
|
|
| New author | npm/unique-slug@3.0.0 |
|
Next steps
What is new author?
A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.
What is a deprecated package?
The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.
Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.
What is network access?
This module accesses the network.
Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/@npmcli/fs@2.1.2@SocketSecurity ignore npm/@npmcli/move-file@2.0.1@SocketSecurity ignore npm/are-we-there-yet@3.0.1@SocketSecurity ignore npm/make-fetch-happen@10.2.1@SocketSecurity ignore npm/nopt@6.0.0@SocketSecurity ignore npm/npmlog@6.0.2@SocketSecurity ignore npm/unique-slug@3.0.0