bare-tcp
Native TCP sockets for JavaScript
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Native addon from Holepunch; platform prebuilds are the documented distribution mechanism for bare addons. | ai | |
| dependencies | unvetted-dep:bare-dns | AI (dependencies): bare-dns is a Holepunch ecosystem package consistent with this package's origin and purpose. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 2.5.3 | 3 / 6 | |
| 2.5.2 | 3 / 6 | |
| 2.5.1 | 3 / 6 | |
| 2.5.0 | 3 / 6 | |
| 2.4.2 | 3 / 6 | |
| 2.4.1 | 3 / 6 | |
| 2.4.0 | 3 / 5 | |
| 2.3.2 | 3 / 5 | |
| 2.3.1 | 3 / 5 | |
| 2.3.0 | 3 / 5 | |
| 2.2.13 | 3 / 5 | |
| 2.2.12 | 3 / 5 | |
| 2.2.11 | 3 / 5 | |
| 2.2.10 | 3 / 5 | |
| 2.2.9 | 3 / 5 | |
| 2.2.8 | 3 / 5 | |
| 2.2.7 | 3 / 4 | |
| 2.2.6 | 3 / 4 | |
| 2.2.5 | 3 / 4 | |
| 2.2.4 | 3 / 4 | |
| 2.2.3 | 3 / 4 | |
| 2.2.2 | 3 / 4 | |
| 2.2.1 | 3 / 4 | |
| 2.2.0 | 3 / 4 | |
| 2.1.0 | 3 / 4 | |
| 2.0.9 | 3 / 4 | |
| 2.0.8 | 3 / 4 | |
| 2.0.7 | 3 / 4 | |
| 2.0.6 | 3 / 4 | |
| 2.0.5 | 3 / 4 | |
| 2.0.4 | 3 / 4 | |
| 2.0.3 | 3 / 4 | |
| 2.0.2 | 3 / 4 | |
| 2.0.1 | 3 / 4 | |
| 2.0.0 | 3 / 4 |
v2.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.