web3-eth-iban
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): web3.js is a ChainSafe monorepo that legitimately produces many similarly-named packages (web3-eth-*, web3-utils, etc.). Mass-production signal is a false positive for this ecosystem. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.0.7 | 4 / 12 | |
| 4.0.6 | 4 / 12 | |
| 4.0.5 | 4 / 12 | |
| 4.0.4 | 4 / 12 | |
| 4.0.3 | 4 / 12 | |
| 4.0.2 | 4 / 12 | |
| 4.0.1 | 4 / 12 | |
| 1.10.4 | 2 / 2 |
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.