@libp2p/tls
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from npm-service-account-libp2p to achingbrain is a legitimate org change; achingbrain is the primary js-libp2p maintainer with a strong track record and SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Sub-package of js-libp2p monorepo; dormancy is expected for stable components. SLSA provenance and no material code changes confirm legitimacy. | ai | |
| provenance | slsa-provenance | AI (provenance): Package explicitly enables provenance in publishConfig; SLSA attestation via Sigstore is a stable, expected signal for this package going forward. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): reflect-metadata is a well-known package required by @peculiar/asn1-schema decorators already in the dep tree; addition is consistent with existing dependencies. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @libp2p/tls is part of the official js-libp2p monorepo; Levenshtein comparison to 'qs' is a false positive with no plausible impersonation intent. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 3.1.3 | 14 / 5 | |
| 3.1.2 | 14 / 5 | |
| 3.1.1 | 14 / 5 | |
| 3.1.0 | 14 / 5 | |
| 3.0.17 | 14 / 5 | |
| 3.0.15 | 13 / 5 | |
| 3.0.14 | 13 / 5 | |
| 3.0.13 | 13 / 5 | |
| 3.0.12 | 13 / 5 | |
| 3.0.11 | 13 / 5 | |
| 3.0.10 | 13 / 5 | |
| 3.0.9 | 13 / 5 | |
| 3.0.8 | 13 / 5 | |
| 3.0.7 | 13 / 5 | |
| 3.0.6 | 13 / 5 | |
| 3.0.5 | 13 / 5 | |
| 3.0.4 | 13 / 5 | |
| 3.0.3 | 13 / 5 | |
| 3.0.2 | 13 / 5 | |
| 3.0.1 | 13 / 5 | |
| 3.0.0 | 13 / 5 |
v3.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.17
2 findingsThis version was published by a different npm account than previous versions on 2026-04-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.13
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.12
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.10
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.