socket-security[bot]
commented
7 months ago New dependencies detected. Learn more about Socket for GitHub ↗︎
Closed garrettbear closed 4 months ago
socket-security[bot]
commented
7 months ago New dependencies detected. Learn more about Socket for GitHub ↗︎
socket-security[bot]
commented
7 months ago 🚨 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/find-yarn-workspace-root@2.0.0 | ||
| New author | npm/jsonify@0.0.1 |
| |
| New author | npm/postcss-value-parser@3.3.1 |
| |
| New author | npm/util@0.10.4 |
| |
| New author | npm/emitter-component@1.1.2 |
| |
| Install scripts | npm/@bundled-es-modules/glob@10.3.13 |
| |
| New author | npm/jsonc-parser@3.2.1 |
| |
| Install scripts | npm/style-dictionary@4.0.0-prerelease.13 |
|
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.
Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.
Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.
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.
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.
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/find-yarn-workspace-root@2.0.0@SocketSecurity ignore npm/jsonify@0.0.1@SocketSecurity ignore npm/postcss-value-parser@3.3.1@SocketSecurity ignore npm/util@0.10.4@SocketSecurity ignore npm/emitter-component@1.1.2@SocketSecurity ignore npm/@bundled-es-modules/glob@10.3.13@SocketSecurity ignore npm/jsonc-parser@3.2.1@SocketSecurity ignore npm/style-dictionary@4.0.0-prerelease.13
georgewrmarshall
commented
4 months ago Closing for now
Description
To run:
node style-dictionary-build.jsRelated issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist