Closed shilman closed 1 year ago
socket-security[bot]
commented
1 year ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Packages | Version | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|---|
| auto | 10.46.0 | eval | +124 |
17.9 MB | alisowski |
🚮 Removed packages: react@18.2.0, react-dom@18.2.0
socket-security[bot]
commented
1 year 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.
| Issue | Package | Version | Note | Source |
|---|---|---|---|---|
| New author | supports-hyperlinks | 2.3.0 |
|
|
| New author | signale | 1.4.0 |
|
|
| Shell access | @auto-it/core | 10.46.0 |
|
|
| Shell access | @auto-it/npm | 10.46.0 |
|
|
| Shell access | bottleneck | 2.19.5 |
|
|
| Uses eval | bottleneck | 2.19.5 |
|
|
| Shell access | gitlog | 4.0.8 |
|
|
| Shell access | requireg | 0.2.2 |
|
|
| Shell access | ts-node | 10.9.1 |
|
|
| Uses eval | await-to-js | 3.0.0 |
|
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.
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.
Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Avoid packages that use eval, since this could potentially execute any code.
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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore await-to-js@3.0.0@SocketSecurity ignore bottleneck@2.19.5@SocketSecurity ignore supports-hyperlinks@2.3.0@SocketSecurity ignore signale@1.4.0@SocketSecurity ignore @auto-it/core@10.46.0@SocketSecurity ignore @auto-it/npm@10.46.0@SocketSecurity ignore gitlog@4.0.8@SocketSecurity ignore requireg@0.2.2@SocketSecurity ignore ts-node@10.9.1
What I did
How to test
@storybook/addon-designsis installable in a fresh project on your machine📦 Published PR as canary version:
7.0.0--canary.198.a3d6b5a.0:sparkles: Test out this PR locally via: ```bash npm install @storybook/addon-designs@7.0.0--canary.198.a3d6b5a.0 # or yarn add @storybook/addon-designs@7.0.0--canary.198.a3d6b5a.0 ```