Use shared constants #25
Pull Request #25 Alerts: Complete with warnings
| Report | Status | Message |
|---|---|---|
| PR #25 Alerts | Found 7 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 | CI |
|---|---|---|---|---|
| License Policy Violation | npm/jsbn@1.1.0 |
| ⚠︎ | |
| License Policy Violation | npm/spdx-exceptions@2.5.0 |
| ⚠︎ | |
| Unstable ownership | npm/@npmcli/fs@4.0.0 |
| ⚠︎ | |
| Unstable ownership | npm/unique-filename@4.0.0 |
| ⚠︎ | |
| Unstable ownership | npm/unique-slug@5.0.0 |
| ⚠︎ | |
| Unstable ownership | npm/@npmcli/node-gyp@4.0.0 |
| ⚠︎ | |
| License Policy Violation | npm/caniuse-lite@1.0.30001688 |
| ⚠︎ |
Next steps
What is a license policy violation?
This package is not allowed per your license policy. Review the package's license to ensure compliance.
Find a package that does not violate your license policy or adjust your policy to allow this package's license.
What is unstable ownership?
A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.
Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.
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/jsbn@1.1.0@SocketSecurity ignore npm/spdx-exceptions@2.5.0@SocketSecurity ignore npm/@npmcli/fs@4.0.0@SocketSecurity ignore npm/unique-filename@4.0.0@SocketSecurity ignore npm/unique-slug@5.0.0@SocketSecurity ignore npm/@npmcli/node-gyp@4.0.0@SocketSecurity ignore npm/caniuse-lite@1.0.30001688