Bump json5 and webpack #48
Pull Request #48 Alerts: Complete with warnings
| Report | Status | Message |
|---|---|---|
| PR #48 Alerts | Found 17 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.
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.
Why is contributor and author data important?
Package does not specify a list of contributors or an author in package.json.
Add a author field or contributors array to package.json.
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.
Why are READMEs important?
Package does not have a README. This may indicate a failed publish or a low quality package.
Add a README to to the package and publish a new version.
What is an invalid package.json?
Package has an invalid package.json and can cause installation problems if you try to use it.
Fix syntax errors in the invalid package.json and publish a new version with a valid package.json. Consumers can use npm overrides to force a version that does not have this problem if one exists.
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
@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/@webassemblyjs/[email protected]@SocketSecurity ignore npm/@webassemblyjs/[email protected]@SocketSecurity ignore npm/@webassemblyjs/[email protected]@SocketSecurity ignore npm/@webassemblyjs/[email protected]@SocketSecurity ignore npm/@webassemblyjs/[email protected]@SocketSecurity ignore npm/@webassemblyjs/[email protected]@SocketSecurity ignore npm/@webassemblyjs/[email protected]@SocketSecurity ignore npm/@webassemblyjs/[email protected]@SocketSecurity ignore npm/@webassemblyjs/[email protected]@SocketSecurity ignore npm/@webassemblyjs/[email protected]@SocketSecurity ignore npm/[email protected]