@peerbit/shared-log
Shared log
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established peerbit ecosystem package; sparse README/keywords are a style choice, not spam. | ai | |
| phantom-deps | phantom-dep:@peerbit/indexer-sqlite3 | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Listed in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:pidusage | AI (phantom-deps): Listed in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@peerbit/any-store | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@libp2p/crypto | AI (phantom-deps): Listed in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:json-stringify-deterministic | AI (phantom-deps): Listed in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:p-each-series | AI (phantom-deps): Listed in dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 13.1.18 | 26 / 5 | |
| 13.1.17 | 26 / 5 | |
| 13.1.16 | 25 / 4 | |
| 13.1.15 | 25 / 4 | |
| 13.1.14 | 25 / 4 | |
| 13.1.13 | 25 / 4 | |
| 13.1.10 | 25 / 4 | |
| 13.1.8 | 25 / 4 | |
| 13.1.4 | 25 / 4 | |
| 13.1.2 | 25 / 4 | |
| 13.1.1 | 25 / 4 | |
| 13.0.5 | 25 / 4 |
v13.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.