@eth-optimism/contracts
[Optimism] L1 and L2 smart contracts for Optimism
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ethersproject/abstract-provider | AI (phantom-deps): Used indirectly in build/config tooling. | ai | |
| dependencies | unvetted-dep:@eth-optimism/solc | AI (dependencies): First-party Optimism compiler dep, expected for this package. | ai | |
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer; no source-integrity concern for this trusted package. | ai | |
| dependencies | unvetted-dep:@nomiclabs/hardhat-etherscan | AI (dependencies): Established hardhat ecosystem dep, benign for this package. | ai | |
| dependencies | unvetted-dep:@ethersproject/hardware-wallets | AI (dependencies): Official ethersproject package, standard ethers.js ecosystem dep. | ai | |
| source-diff | obfuscated-file:dist/types/factories/contracts/L1/rollup/ChainStorageContainer__factory.ts | AI (source-diff): TypeChain autogenerated factory; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types/factories/contracts/L1/rollup/CanonicalTransactionChain__factory.ts | AI (source-diff): TypeChain autogenerated factory; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types/factories/@openzeppelin/contracts/token/ERC20/ERC20__factory.ts | AI (source-diff): TypeChain autogenerated factory; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types/factories/contracts/L1/deployment/ChugSplashDictator__factory.ts | AI (source-diff): TypeChain autogenerated factory; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types/factories/contracts/L1/deployment/AddressDictator__factory.ts | AI (source-diff): TypeChain autogenerated factory with long ABI lines; not obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Large size increase is deployment artifacts, not injected code. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Deployment solcInput JSON dumps for mainnet/goerli/kovan, expected for contracts package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): karlfloersch is a known long-standing maintainer per provenance info. | ai | |
| phantom-deps | phantom-dep:@ethersproject/hardware-wallets | AI (phantom-deps): Config-only usage typical for this build tooling. | ai | |
| phantom-deps | phantom-dep:@ethersproject/contracts | AI (phantom-deps): Config-only usage typical for this build tooling. | ai | |
| phantom-deps | phantom-dep:@openzeppelin/contracts | AI (phantom-deps): Used via Solidity imports in contracts, not JS require. | ai | |
| dependencies | unvetted-dep:@eth-optimism/core-utils | AI (dependencies): Sibling package from the same ethereum-optimism monorepo; published by the same organization. Unvetted status is a pipeline artifact, not a real risk. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 3 / 51 | |
| 0.5.33 | 3 / 51 | |
| 0.5.32 | 3 / 51 | |
| 0.5.31 | 3 / 51 | |
| 0.5.30 | 3 / 51 | |
| 0.5.29 | 3 / 51 | |
| 0.5.28 | 3 / 51 | |
| 0.5.27 | 3 / 50 | |
| 0.5.26 | 3 / 50 | |
| 0.5.25 | 3 / 61 | |
| 0.5.11 | 4 / 57 | |
| 0.5.10 | 4 / 57 | |
| 0.4.11 | 7 / 57 | |
| 0.1.8 | 6 / 36 | |
| 0.1.2 | 7 / 33 | |
| 0.1.0 | 6 / 33 | |
| 0.0.1 | 0 / 30 |
v0.5.33
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-08-25, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.32
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-08-04, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.31
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-07-25, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.30
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-07-12, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.29
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-06-23, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.28
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-06-15, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.27
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-06-08, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.26
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-06-02, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.25
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-06-01, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-01-31, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2022-01-28, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.11
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2021-09-08, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (karlfloersch) than the most recent previously approved version (tynes) on 2021-01-13, but karlfloersch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.