Closed Data-Nexus closed 7 months ago
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@graphprotocol/graph-cli@0.20.1, npm/@graphprotocol/graph-ts@0.20.0, npm/debug@4.3.1, npm/picomatch@2.2.3, npm/signal-exit@3.0.3
🚨 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 |
---|---|---|---|
Install scripts | npm/protobufjs@6.11.4 |
| |
Native code | npm/secp256k1@4.0.3 |
| |
Native code | npm/keccak@3.0.4 |
| |
Deprecated | npm/multiaddr-to-uri@8.0.0 |
| |
Deprecated | npm/ipfs-core-types@0.9.0 |
| |
Deprecated | npm/ipfs-core-utils@0.13.0 |
|
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.
Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.
Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.
The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.
Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.
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/protobufjs@6.11.4
@SocketSecurity ignore npm/secp256k1@4.0.3
@SocketSecurity ignore npm/keccak@3.0.4
@SocketSecurity ignore npm/multiaddr-to-uri@8.0.0
@SocketSecurity ignore npm/ipfs-core-types@0.9.0
@SocketSecurity ignore npm/ipfs-core-utils@0.13.0
Builds to: QmRT4bfsKTkgiV7KVS1uu6tVFtxhE38UmpiMoFFZmQvbJE
link for tesing: https://thegraph.com/hosted-service/subgraph/graph-buildersdao/univ3-arbitrum-minimal
Fixes:
less than 255
check infetchTokenDecimals()