@libp2p/interface-connection
Connection interface for libp2p
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from achingbrain to npm-service-account-libp2p reflects libp2p org's move to a shared CI/CD service account. The new publisher has 242 approved packages and is the official libp2p npm account. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jacobheun is a known libp2p contributor; npm-service-account-libp2p is the official libp2p publishing account. This is a legitimate organizational maintainer transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): uint8arraylist is a legitimate libp2p ecosystem package for efficient byte array handling, widely used across libp2p packages. Not a suspicious dependency. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a standard placeholder version used by semantic-release in monorepo setups; package.json confirms this workflow. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread Sigstore provenance adoption; published by the trusted libp2p service account with a clean track record. | ai | |
| dependencies | unvetted-dep:@libp2p/interfaces | AI (dependencies): @libp2p/interfaces is a sibling package in the same libp2p ecosystem, published by the same trusted org. No security concern. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 5 / 1 | |
| 5.1.0 | 5 / 1 | |
| 5.0.2 | 5 / 1 | |
| 5.0.1 | 5 / 1 | |
| 5.0.0 | 5 / 1 | |
| 4.0.0 | 5 / 1 | |
| 3.1.1 | 5 / 1 | |
| 3.1.0 | 5 / 1 | |
| 3.0.8 | 5 / 1 | |
| 3.0.7 | 5 / 1 | |
| 3.0.6 | 5 / 1 | |
| 3.0.5 | 5 / 1 | |
| 3.0.4 | 5 / 1 | |
| 3.0.3 | 5 / 1 | |
| 3.0.2 | 5 / 1 | |
| 3.0.1 | 5 / 1 | |
| 3.0.0 | 5 / 1 | |
| 2.1.1 | 4 / 1 | |
| 2.1.0 | 4 / 1 | |
| 2.0.0 | 4 / 1 | |
| 1.0.1 | 4 / 1 | |
| 1.0.0 | 4 / 1 | |
| 0.0.0 | 5 / 1 |
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
2 findingsThis version was published by a different npm account than previous versions on 2023-03-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2023-03-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
2 findingsThis version was published by a different npm account than previous versions on 2023-01-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
2 findingsThis version was published by a different npm account than previous versions on 2023-01-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
2 findingsThis version was published by a different npm account than previous versions on 2022-12-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
2 findingsThis version was published by a different npm account than previous versions on 2022-12-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
2 findingsThis version was published by a different npm account than previous versions on 2022-12-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
2 findingsThis version was published by a different npm account than previous versions on 2022-11-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsThis version was published by a different npm account than previous versions on 2022-09-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-08-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-08-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.