@bsv/p2p
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @bsv package from BSV Blockchain Association; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @bsv package from BSV Blockchain Association; not a typosquat of yup. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is in a test file as a benign message encoding helper, not a payload loader. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.1.6 | 2 / 26 | |
| 1.1.5 | 2 / 26 | |
| 1.1.4 | 2 / 26 | |
| 1.1.3 | 2 / 26 | |
| 1.1.2 | 2 / 26 |
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.