Closed dependabot[bot] closed 4 months ago
socket-security[bot]
commented
4 months ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|
| npm/terser@5.31.1 | None | 0 |
0 B |
🚮 Removed packages: npm/terser@5.31.0
socket-security[bot]
commented
4 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 |
|---|---|---|
| Filesystem access | npm/source-map-support@0.5.21 |
|
| Environment variable access | npm/terser@5.31.0 |
|
| Uses eval | npm/terser@5.31.0 |
|
| Uses eval | npm/terser@5.31.0 |
|
| Environment variable access | npm/terser@5.31.0 |
|
| Environment variable access | npm/terser@5.31.0 |
|
| Environment variable access | npm/terser@5.31.0 |
|
| Environment variable access | npm/terser@5.31.0 |
|
Accesses the file system, and could potentially read sensitive data.
If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.
Package accesses environment variables, which may be a sign of credential stuffing or data theft.
Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.
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 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/source-map-support@0.5.21@SocketSecurity ignore npm/terser@5.31.0
Bumps terser from 5.31.0 to 5.31.1.
Changelog
Sourced from terser's changelog.
Commits
57ea5925.31.1cf57d77fix normalization of AST_Sequence14cc291avoid drop-unused leaving behind the contents of an assignment. Related to we...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show