Maintenance: Update to yarn berry #344
Pull Request #344 Alerts: Complete with warnings
| Report | Status | Message |
|---|---|---|
| PR #344 Alerts | Found 12 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.
| Issue | Package | Version | Note | Source |
|---|---|---|---|---|
| Bin script confusion | storybook | 7.3.1 |
|
|
| Bin script confusion | storybook | 7.3.2 |
|
|
| New author | istanbul-lib-report | 3.0.1 |
|
|
| New author | handlebars | 4.7.8 | ||
| New author | nopt | 6.0.0 | ||
| Shell access | node-gyp | 9.4.0 |
|
Next steps
What is bin script confusion?
This package has multiple bin scripts with the same name. This can cause non-deterministic behavior when installing or could be a sign of a supply chain attack
Consider removing one of the conflicting packages. Packages should only export bin scripts with their name
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 shell access?
This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.
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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore istanbul-lib-report@3.0.1@SocketSecurity ignore handlebars@4.7.8@SocketSecurity ignore nopt@6.0.0@SocketSecurity ignore node-gyp@9.4.0@SocketSecurity ignore storybook@7.3.1@SocketSecurity ignore storybook@7.3.2