← Home

eth-connect

npm Repository Homepage

Ethereum TypeScript API, middleware to talk to a ethereum node using an async provider

11
Versions
LGPL-3.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

cazalamenduzdecentralandbot

Keywords

ethereumtypescriptweb3json-rpcethAPI

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to CI/CD publishing with SLSA attestation is a security improvement, not compromise. ai
publish-pattern rapid-publish AI (publish-pattern): Likely CI republish/tag fix; no material diff from prior version. ai

Versions (showing 11 of 11)

Version Deps Published
6.4.0 0 / 0
6.3.1 0 / 0
6.2.4 0 / 0
6.2.2 0 / 0
6.2.1 0 / 0
6.2.0 0 / 0
6.1.0 0 / 0
6.0.3 0 / 0
6.0.2 0 / 0
6.0.1 0 / 0
6.0.0 0 / 0

v6.2.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.2.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v6.2.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v6.1.0

1 finding
LOW No provenance attestation provenance

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

v6.0.3

1 finding
LOW No provenance attestation provenance

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

v6.0.2

1 finding
LOW No provenance attestation provenance

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

v6.0.1

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.

v6.0.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.