← Home

@libp2p/config

npm Repository Homepage
39
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

daviddiasalanshawachingbrainvascosantosnpm-service-account-libp2pjacobheun

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from achingbrain to GitHub Actions reflects legitimate CI/CD automation for the libp2p org; SLSA provenance attestation confirms build integrity. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD-published release with SLSA attestation for an established libp2p org package; no material code changes indicate routine maintenance. ai
dependencies unvetted-dep:@libp2p/keychain AI (dependencies): @libp2p/keychain is a first-party package from the same libp2p monorepo; this intra-ecosystem dependency is expected and stable across versions. ai

Versions (showing 39 of 39)

Version Deps Published
1.1.35 5 / 2
1.1.34 5 / 2
1.1.33 5 / 2
1.1.32 5 / 2
1.1.31 5 / 2
1.1.30 5 / 2
1.1.29 5 / 2
1.1.27 5 / 2
1.1.26 5 / 2
1.1.25 5 / 2
1.1.24 5 / 2
1.1.23 5 / 2
1.1.22 5 / 2
1.1.21 5 / 2
1.1.20 5 / 2
1.1.19 5 / 2
1.1.18 5 / 2
1.1.17 5 / 2
1.1.16 5 / 2
1.1.15 5 / 2
1.1.14 5 / 2
1.1.13 5 / 2
1.1.12 5 / 2
1.1.11 5 / 2
1.1.10 5 / 2
1.1.9 5 / 2
1.1.8 5 / 2
1.1.7 5 / 2
1.1.6 5 / 2
1.1.5 5 / 2
1.1.4 5 / 2
1.1.3 5 / 2
1.1.2 5 / 2
1.1.1 5 / 2
1.1.0 5 / 2
1.0.3 5 / 2
1.0.2 5 / 2
1.0.1 5 / 2
1.0.0 5 / 2

v1.1.35

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.

v1.1.34

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.

v1.1.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.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.