← Home

@acala-network/eth-providers

npm
4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

xlcaniianttqwer951123shunjizhan

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Monorepo sub-package; missing metadata is a style choice, not a spam/malware signal for this established org. ai
phantom-deps phantom-dep:graphql AI (phantom-deps): graphql is a declared runtime dep used via graphql-request; phantom-dep heuristic fires but it's a stable false positive here. ai
phantom-deps phantom-dep:@acala-network/contracts AI (phantom-deps): Same-org dep; phantom-dep heuristic is unreliable for ABI/type-only imports common in blockchain packages. ai

Versions (showing 4 of 4)

Version Deps Published
2.10.0 7 / 6
2.9.9 7 / 6
2.9.8 7 / 6
2.9.7 7 / 6

v2.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.9.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.9.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.9.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.