@ethersproject/abi
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): False positive: @ethersproject/abi is a legitimate scoped package in the ethers.js ecosystem, not a typosquat of 'hapi'. Levenshtein match on short suffix 'abi' is meaningless. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): False positive: @ethersproject/abi is a legitimate scoped package in the ethers.js ecosystem, not a typosquat of 'joi'. Levenshtein match on short suffix 'abi' is meaningless. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): False positive: @ethersproject/abi is a legitimate scoped package in the ethers.js ecosystem, not a typosquat of 'ajv'. Levenshtein match on short suffix 'abi' is meaningless. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 5.8.0 | 9 / 0 | |
| 5.7.0 | 9 / 0 | |
| 5.6.4 | 9 / 0 | |
| 5.6.3 | 9 / 0 | |
| 5.6.2 | 9 / 0 | |
| 5.6.1 | 9 / 0 | |
| 5.6.0 | 9 / 0 | |
| 5.5.0 | 9 / 0 | |
| 5.4.1 | 9 / 0 | |
| 5.4.0 | 9 / 0 | |
| 5.3.1 | 9 / 0 | |
| 5.3.0 | 9 / 0 | |
| 5.2.0 | 9 / 0 | |
| 5.1.2 | 9 / 0 | |
| 5.1.1 | 9 / 0 | |
| 5.1.0 | 9 / 0 | |
| 5.0.13 | 9 / 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.