@orderly.network/web3-provider-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 — the axios compromise (March 2026) relied on exactly this gap.
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): Established scoped org package; missing metadata is a style choice, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across the @orderly.network package family; not a risk signal here. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 4 / 4 | |
| 3.0.4 | 4 / 4 | |
| 3.0.3 | 4 / 4 | |
| 3.0.2 | 4 / 4 | |
| 3.0.1 | 4 / 4 | |
| 3.0.0 | 4 / 4 | |
| 2.12.4 | 4 / 4 | |
| 2.12.3 | 4 / 4 | |
| 2.12.2 | 4 / 4 | |
| 2.12.1 | 4 / 4 | |
| 2.12.0 | 4 / 4 | |
| 2.11.2 | 4 / 4 | |
| 2.11.1 | 4 / 4 | |
| 2.11.0 | 4 / 4 | |
| 2.10.2 | 4 / 4 | |
| 2.10.1 | 4 / 4 | |
| 2.10.0 | 4 / 4 | |
| 2.9.1 | 4 / 4 | |
| 2.9.0 | 4 / 4 | |
| 2.8.14 | 4 / 4 | |
| 2.8.13 | 4 / 4 | |
| 2.8.12 | 4 / 4 | |
| 2.8.11 | 4 / 4 | |
| 2.8.10 | 4 / 4 | |
| 2.8.9 | 4 / 4 | |
| 2.8.8 | 4 / 4 | |
| 2.8.7 | 4 / 4 | |
| 2.8.6 | 4 / 4 | |
| 2.8.5 | 4 / 4 | |
| 2.8.4 | 4 / 4 | |
| 2.8.3 | 4 / 4 | |
| 2.8.2 | 4 / 4 |
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.