@peerbit/document
Document store implementation
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@libp2p/tcp | AI (phantom-deps): Referenced in config/test files only; not a runtime import concern for this package. | ai | |
| phantom-deps | phantom-dep:@peerbit/pubsub | AI (phantom-deps): Same-org peer dependency; used indirectly via @peerbit ecosystem, stable false positive. | ai | |
| phantom-deps | phantom-dep:@chainsafe/libp2p-yamux | AI (phantom-deps): Config-file reference only; not a direct runtime import. | ai | |
| phantom-deps | phantom-dep:@peerbit/indexer-sqlite3 | AI (phantom-deps): Same-org optional indexer backend; stable false positive for this package. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 13.0.44 | 21 / 8 | |
| 13.0.43 | 21 / 8 | |
| 13.0.42 | 21 / 8 | |
| 13.0.41 | 21 / 8 | |
| 13.0.40 | 21 / 8 | |
| 13.0.39 | 21 / 8 | |
| 13.0.38 | 21 / 8 | |
| 13.0.37 | 21 / 8 | |
| 13.0.36 | 21 / 8 | |
| 13.0.35 | 21 / 8 | |
| 13.0.34 | 21 / 8 | |
| 13.0.33 | 21 / 8 | |
| 13.0.32 | 21 / 8 | |
| 13.0.31 | 21 / 8 | |
| 13.0.30 | 21 / 8 | |
| 13.0.29 | 21 / 8 | |
| 13.0.28 | 21 / 8 | |
| 13.0.27 | 21 / 8 | |
| 13.0.26 | 21 / 8 | |
| 13.0.25 | 21 / 8 | |
| 13.0.24 | 21 / 8 | |
| 13.0.23 | 21 / 8 | |
| 13.0.22 | 21 / 8 | |
| 13.0.21 | 21 / 8 | |
| 13.0.20 | 21 / 8 | |
| 13.0.19 | 21 / 8 | |
| 13.0.18 | 21 / 8 | |
| 13.0.17 | 21 / 8 | |
| 13.0.16 | 21 / 8 | |
| 13.0.15 | 21 / 8 | |
| 13.0.14 | 21 / 8 | |
| 13.0.13 | 21 / 8 | |
| 13.0.12 | 21 / 8 | |
| 13.0.11 | 21 / 8 | |
| 13.0.10 | 21 / 8 | |
| 13.0.9 | 21 / 8 | |
| 13.0.8 | 21 / 8 | |
| 13.0.7 | 21 / 8 | |
| 13.0.6 | 21 / 8 | |
| 13.0.5 | 21 / 8 | |
| 13.0.4 | 21 / 8 | |
| 13.0.3 | 21 / 8 | |
| 13.0.2 | 21 / 8 | |
| 13.0.0 | 21 / 8 | |
| 12.3.5 | 21 / 8 | |
| 12.3.4 | 21 / 8 | |
| 12.3.3 | 21 / 8 | |
| 12.3.2 | 21 / 8 | |
| 12.3.1 | 21 / 8 | |
| 12.3.0 | 21 / 8 | |
| 12.2.0 | 21 / 8 | |
| 12.1.2 | 21 / 8 | |
| 12.1.1 | 21 / 8 | |
| 11.2.7 | 21 / 8 | |
| 11.2.6 | 21 / 8 | |
| 11.2.4 | 21 / 8 | |
| 11.2.3 | 21 / 8 | |
| 11.2.2 | 21 / 8 | |
| 11.2.1 | 21 / 8 | |
| 11.2.0 | 21 / 8 | |
| 11.1.1 | 21 / 8 | |
| 11.1.0 | 21 / 8 | |
| 11.0.0 | 21 / 8 | |
| 10.1.3 | 21 / 8 | |
| 10.1.2 | 21 / 8 | |
| 10.1.1 | 21 / 8 | |
| 10.1.0 | 21 / 8 |
v13.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.