@openzeppelin/upgrades-core
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:fp-ts | AI (phantom-deps): fp-ts/io-ts ecosystem dep likely used indirectly; not a malicious install-script vector. | ai | |
| provenance | missing-githead | AI (provenance): Established OZ package; missing gitHead reflects publish-env change, no malicious behavior. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long gap explained by CI migration; package is actively maintained on GitHub. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual maintainer to GitHub Actions CI/CD; consistent with SLSA provenance attestation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Empty description is a metadata oversight on a well-known package. | ai | |
| dependencies | unvetted-dep:ethereumjs-util | AI (dependencies): ethereumjs-util is a standard Ethereum utility library; its use is expected and appropriate in an Ethereum upgrade tooling package. | ai | |
| dependencies | unvetted-dep:@nomicfoundation/slang | AI (dependencies): @nomicfoundation/slang is a Solidity parser from Nomic Foundation (Hardhat team), a reputable Ethereum org. Appropriate dependency for Solidity upgrade analysis tooling. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in this package is standard Ethereum ABI data parsing (stripping 0x prefix from on-chain encoded strings). No obfuscation or malicious payload; stable false positive for this package. | ai |
Versions (showing 100 of 104)
| Version | Deps | Published |
|---|---|---|
| 1.46.0 | 11 / 16 | |
| 1.45.0 | 11 / 16 | |
| 1.44.2 | 11 / 16 | |
| 1.44.1 | 11 / 16 | |
| 1.44.0 | 11 / 16 | |
| 1.43.0 | 10 / 16 | |
| 1.42.2 | 10 / 16 | |
| 1.42.1 | 10 / 16 | |
| 1.42.0 | 10 / 16 | |
| 1.41.0 | 10 / 16 | |
| 1.40.0 | 10 / 16 | |
| 1.39.0 | 10 / 16 | |
| 1.38.0 | 10 / 16 | |
| 1.37.1 | 10 / 16 | |
| 1.37.0 | 10 / 16 | |
| 1.36.0 | 9 / 16 | |
| 1.35.1 | 9 / 16 | |
| 1.35.0 | 9 / 16 | |
| 1.34.4 | 8 / 16 | |
| 1.34.3 | 8 / 16 | |
| 1.34.2 | 8 / 16 | |
| 1.34.1 | 8 / 16 | |
| 1.34.0 | 8 / 16 | |
| 1.33.1 | 8 / 16 | |
| 1.33.0 | 8 / 16 | |
| 1.32.6 | 8 / 16 | |
| 1.32.5 | 8 / 17 | |
| 1.32.4 | 8 / 17 | |
| 1.32.3 | 8 / 17 | |
| 1.32.2 | 8 / 17 | |
| 1.32.1 | 8 / 17 | |
| 1.32.0 | 8 / 17 | |
| 1.31.3 | 8 / 17 | |
| 1.31.2 | 8 / 17 | |
| 1.31.1 | 8 / 17 | |
| 1.31.0 | 8 / 17 | |
| 1.30.1 | 8 / 17 | |
| 1.30.0 | 8 / 17 | |
| 1.29.0 | 8 / 17 | |
| 1.28.0 | 8 / 17 | |
| 1.27.3 | 8 / 17 | |
| 1.27.2 | 8 / 17 | |
| 1.27.1 | 8 / 18 | |
| 1.27.0 | 8 / 18 | |
| 1.26.2 | 7 / 18 | |
| 1.26.1 | 7 / 18 | |
| 1.26.0 | 7 / 18 | |
| 1.25.0 | 7 / 17 | |
| 1.24.1 | 7 / 17 | |
| 1.24.0 | 7 / 17 | |
| 1.23.0 | 7 / 17 | |
| 1.22.0 | 7 / 17 | |
| 1.21.0 | 7 / 17 | |
| 1.20.6 | 7 / 17 | |
| 1.20.5 | 7 / 17 | |
| 1.20.4 | 7 / 17 | |
| 1.20.3 | 7 / 17 | |
| 1.20.2 | 7 / 17 | |
| 1.20.1 | 7 / 17 | |
| 1.20.0 | 7 / 17 | |
| 1.19.1 | 7 / 17 | |
| 1.19.0 | 7 / 17 | |
| 1.18.0 | 7 / 17 | |
| 1.17.0 | 7 / 17 | |
| 1.16.1 | 8 / 18 | |
| 1.16.0 | 8 / 18 | |
| 1.15.0 | 8 / 18 | |
| 1.14.2 | 8 / 18 | |
| 1.14.1 | 8 / 18 | |
| 1.14.0 | 8 / 18 | |
| 1.13.1 | 8 / 18 | |
| 1.13.0 | 8 / 18 | |
| 1.12.0 | 8 / 18 | |
| 1.11.1 | 8 / 18 | |
| 1.11.0 | 8 / 18 | |
| 1.10.0 | 8 / 18 | |
| 1.9.2 | 8 / 18 | |
| 1.9.1 | 8 / 17 | |
| 1.9.0 | 8 / 17 | |
| 1.8.1 | 8 / 17 | |
| 1.8.0 | 8 / 17 | |
| 1.7.6 | 8 / 17 | |
| 1.7.5 | 8 / 17 | |
| 1.7.4 | 8 / 17 | |
| 1.7.3 | 8 / 17 | |
| 1.7.2 | 10 / 17 | |
| 1.7.1 | 10 / 17 | |
| 1.7.0 | 10 / 17 | |
| 1.6.0 | 10 / 16 | |
| 1.5.1 | 10 / 16 | |
| 1.5.0 | 10 / 16 | |
| 1.4.4 | 10 / 16 | |
| 1.4.3 | 10 / 16 | |
| 1.4.2 | 10 / 16 | |
| 1.4.1 | 10 / 15 | |
| 1.4.0 | 10 / 15 | |
| 1.3.1 | 10 / 15 | |
| 1.3.0 | 10 / 15 | |
| 1.2.0 | 10 / 14 | |
| 1.1.1 | 10 / 13 |
v1.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ericglau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ericglau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ericglau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ericglau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
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: frangio.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (frangio) than the most recent previously approved version (ericglau) on 2023-05-12, but frangio 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.
v1.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
2 findingsThis version was published by a different npm account (ericglau) than the most recent previously approved version (frangio) on 2022-01-20. It has since remained available on npm for 1642 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.