@ethersproject/bignumber
BigNumber library used in ethers.js.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ethersproject/bytes | AI (dependencies): Sibling package in the ethers.js monorepo, published by the same maintainer (ricmoo). Unvetted status is a pipeline artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@ethersproject/logger | AI (dependencies): Sibling package in the ethers.js monorepo, published by the same maintainer (ricmoo). Unvetted status is a pipeline artifact, not a real risk. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread Sigstore adoption on npm; absence of provenance is expected for this era of ethers.js releases. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 5.8.0 | 3 / 0 | |
| 5.7.0 | 3 / 0 | |
| 5.6.2 | 3 / 0 | |
| 5.6.1 | 3 / 0 | |
| 5.6.0 | 3 / 0 | |
| 5.5.0 | 3 / 0 | |
| 5.4.2 | 3 / 0 | |
| 5.4.1 | 3 / 0 | |
| 5.4.0 | 3 / 0 | |
| 5.3.0 | 3 / 0 | |
| 5.2.0 | 3 / 0 | |
| 5.1.1 | 3 / 0 | |
| 5.1.0 | 3 / 0 | |
| 5.0.15 | 3 / 0 | |
| 5.0.14 | 3 / 0 | |
| 5.0.13 | 3 / 0 | |
| 5.0.12 | 3 / 0 | |
| 5.0.11 | 3 / 0 | |
| 5.0.10 | 3 / 0 | |
| 5.0.9 | 3 / 0 | |
| 5.0.8 | 3 / 0 | |
| 5.0.7 | 3 / 0 | |
| 5.0.6 | 3 / 0 | |
| 5.0.5 | 3 / 0 | |
| 5.0.4 | 4 / 0 | |
| 5.0.3 | 4 / 0 | |
| 5.0.2 | 4 / 0 | |
| 5.0.1 | 4 / 0 | |
| 5.0.0 | 4 / 0 |
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.