@peerbit/blocks
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:p-defer | AI (phantom-deps): Declared dependency; used transitively in this package's ecosystem. | ai | |
| phantom-deps | phantom-dep:@libp2p/tcp | AI (phantom-deps): Declared dependency; used transitively in this package's ecosystem. | ai | |
| phantom-deps | phantom-dep:uint8arrays | AI (phantom-deps): Declared dependency; used transitively in this package's ecosystem. | ai | |
| phantom-deps | phantom-dep:@ipld/dag-cbor | AI (phantom-deps): Declared dependency; used transitively in this package's ecosystem. | ai | |
| phantom-deps | phantom-dep:@libp2p/websockets | AI (phantom-deps): Declared dependency; used transitively in this package's ecosystem. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 4.1.9 | 18 / 1 | |
| 4.1.8 | 18 / 1 | |
| 4.1.7 | 18 / 1 | |
| 4.1.6 | 18 / 1 | |
| 4.1.5 | 18 / 1 | |
| 4.1.4 | 18 / 1 | |
| 4.1.3 | 18 / 1 | |
| 4.1.2 | 18 / 1 | |
| 4.1.1 | 18 / 1 | |
| 4.1.0 | 18 / 1 | |
| 4.0.11 | 18 / 1 | |
| 4.0.10 | 18 / 1 | |
| 4.0.9 | 18 / 1 | |
| 4.0.8 | 18 / 1 | |
| 4.0.7 | 18 / 1 | |
| 4.0.6 | 18 / 1 | |
| 4.0.5 | 18 / 1 | |
| 4.0.4 | 18 / 1 | |
| 4.0.3 | 18 / 1 | |
| 4.0.2 | 18 / 1 | |
| 4.0.1 | 18 / 1 | |
| 4.0.0 | 18 / 1 | |
| 3.1.8 | 18 / 1 | |
| 3.1.7 | 18 / 1 | |
| 3.1.6 | 18 / 1 | |
| 3.1.5 | 18 / 1 | |
| 3.1.4 | 18 / 1 | |
| 3.1.3 | 18 / 1 | |
| 3.1.2 | 18 / 1 | |
| 3.1.1 | 18 / 1 | |
| 3.1.0 | 18 / 1 |
v4.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.