undiscord
undiscord copied to clipboard
victornpb
Update
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|
| npm/@rollup/[email protected] | Transitive: environment, filesystem | +19 |
36.1 MB | shellscape |
| npm/[email protected] | environment, filesystem Transitive: eval, shell, unsafe | +96 |
10.7 MB | eslintbot |
| npm/[email protected] | environment, filesystem, shell | 0 |
3.61 kB | typicode |
| npm/[email protected] | Transitive: environment, filesystem, shell | +54 |
2.48 MB | okonet |
| npm/[email protected] | environment, filesystem Transitive: shell | +33 |
3.27 MB | isaacs |
| npm/[email protected] | filesystem, network Transitive: shell | +2 |
84.5 kB | thgh |
| npm/[email protected] | environment, filesystem | +15 |
35.8 MB | lukastaegert |
🚮 Removed packages: npm/@rollup/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]
![socket-security[bot] avatar](https://avatars.githubusercontent.com/in/156372?v=4 "Published by a pub.dev verified publisher"){kind=small}
🚨 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 |
|---|---|---|---|
| Dynamic require | npm/[email protected] |
|
Next steps
What is dynamic require?
Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.
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]