@ethersproject/contracts
Contract abstraction meta-class for ethers.
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/constants | AI (phantom-deps): @ethersproject/constants is a sibling package in the same org/monorepo; declaring it without direct import is a benign monorepo pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established ethers.js package predating widespread provenance adoption; no provenance is expected and not a risk signal for this publisher. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 5.8.0 | 10 / 0 | |
| 5.7.0 | 10 / 0 | |
| 5.6.2 | 10 / 0 | |
| 5.6.1 | 10 / 0 | |
| 5.6.0 | 10 / 0 | |
| 5.5.0 | 10 / 0 | |
| 5.4.1 | 10 / 0 | |
| 5.4.0 | 10 / 0 | |
| 5.3.0 | 10 / 0 | |
| 5.2.0 | 10 / 0 | |
| 5.1.1 | 10 / 0 | |
| 5.1.0 | 10 / 0 | |
| 5.0.12 | 9 / 0 | |
| 5.0.11 | 9 / 0 | |
| 5.0.10 | 9 / 0 | |
| 5.0.9 | 9 / 0 | |
| 5.0.8 | 9 / 0 | |
| 5.0.7 | 9 / 0 | |
| 5.0.6 | 9 / 0 | |
| 5.0.5 | 9 / 0 | |
| 5.0.4 | 9 / 0 | |
| 5.0.3 | 9 / 0 | |
| 5.0.2 | 9 / 0 | |
| 5.0.1 | 9 / 0 | |
| 5.0.0 | 9 / 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.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.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. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.