← Home

eth-lib

npm Repository Homepage
5
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

frozemanmaiavictor

Keywords

ethereum

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:xhr2 AI (phantom-deps): Conditional browser/node XHR shim, plausible env-specific import not caught by static scan. ai
dependencies unvetted-dep:elliptic AI (dependencies): elliptic is a widely-used, well-known crypto dep standard for Ethereum libs. ai
phantom-deps phantom-dep:ws AI (phantom-deps): ws is declared as a dependency in this legacy branch of eth-lib; phantom import is a code quality issue, not a security concern for this established package. ai
phantom-deps phantom-dep:servify AI (phantom-deps): servify is declared as a dependency in this legacy branch; phantom import is a code quality issue, not a security concern for this established package. ai
provenance no-provenance AI (provenance): eth-lib is an 8+ year old package predating Sigstore provenance; absence is expected and not a risk signal for this package. ai

Versions (showing 5 of 5)

Version Deps Published
0.2.8 3 / 5
0.1.29 6 / 6
0.1.4 6 / 4
0.1.2 6 / 4
0.1.0 6 / 4

v0.1.4

1 finding
INFO No provenance attestation provenance

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

v0.1.2

1 finding
INFO No provenance attestation provenance

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

v0.1.0

1 finding
INFO No provenance attestation provenance

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