Optimism - Decimal Fix & Graph-ts Upgade

[Data-Nexus]

Fixes:

• Updated graph-ts and cli & AS migrations
• Updated ERC20 ABI to allow larger decimals and add a less than 255 check in fetchTokenDecimals()

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@graphprotocol/graph-cli@0.64.1	Transitive: environment, eval, filesystem, network, shell, unsafe	+499	147 MB	dotansimha
npm/@graphprotocol/graph-ts@0.32.0	Transitive: eval	+3	19.2 MB	dotansimha
npm/typescript@3.9.10	None	0	54.1 MB	typescript-bot

🚮 Removed packages: npm/@graphprotocol/graph-cli@0.20.0, npm/@graphprotocol/graph-ts@0.20.0, npm/@types/node@12.20.12, npm/async@2.6.3, npm/base-x@3.0.8, npm/buffer@5.7.1, npm/cids@0.7.5, npm/console-control-strings@1.1.0, npm/debug@4.3.1, npm/glob@7.1.7, npm/graceful-fs@4.2.6, npm/is-glob@4.0.1, npm/is-promise@1.0.1, npm/iso-url@0.4.7, npm/mime-types@2.1.30, npm/minimatch@3.0.4, npm/minimist@1.2.5, npm/mkdirp-classic@0.5.3, npm/multiaddr@6.1.1, npm/multihashes@0.4.21, npm/nan@2.14.2, npm/peer-id@0.12.5, npm/picomatch@2.2.3, npm/pull-stream@3.6.14, npm/punycode@2.1.1, npm/readable-stream@2.3.7, npm/signal-exit@3.0.3, npm/string-width@2.1.1, npm/tar-stream@2.2.0, npm/typescript@3.9.9, npm/varint@5.0.2

View full report↗︎

[socket-security]

🚨 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	Install script: postinstall Source: node scripts/postinstall	package-lock.json package.json
Native code	npm/secp256k1@4.0.3	Location: Package overview	package-lock.json package.json
Native code	npm/keccak@3.0.4	Location: Package overview	package-lock.json package.json
Deprecated	npm/multiaddr-to-uri@8.0.0	Reason: This module is deprecated, please upgrade to @multiformats/multiaddr-to-uri	package-lock.json package.json
Deprecated	npm/ipfs-core-types@0.9.0	Reason: js-IPFS has been deprecated in favour of Helia - please see https://github.com/[Tracking Issue] js-ipfs deprecation - signposting over to Helia ipfs/js-ipfs#4336 for details	package-lock.json package.json
Deprecated	npm/ipfs-core-utils@0.13.0	Reason: js-IPFS has been deprecated in favour of Helia - please see https://github.com/[Tracking Issue] js-ipfs deprecation - signposting over to Helia ipfs/js-ipfs#4336 for details	package-lock.json package.json

View full report↗︎

Next steps

What is an install script?

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.

What's wrong with native code?

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.

What is a deprecated package?

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 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/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

[Data-Nexus]

Builds to: QmZ1ihSbT8eUTbEu2UfEfoTwhspKFVFZ5vBvDiSB7FFQL5
Link for testing: https://thegraph.com/hosted-service/subgraph/graph-buildersdao/univ3-optimism