@peerbit/log
Append-only log CRDT
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:glob | AI (typosquat): Scoped @peerbit/log is not a typosquat of glob; different namespace entirely. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @peerbit/log is not a typosquat of koa. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @peerbit/log is not a typosquat of got. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @peerbit/log is not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @peerbit/log is not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @peerbit/log is not a typosquat of zod. | ai | |
| phantom-deps | phantom-dep:@peerbit/blocks | AI (phantom-deps): Same-org dep; may be used indirectly via re-exports or type-only imports. | ai | |
| phantom-deps | phantom-dep:@peerbit/indexer-simple | AI (phantom-deps): Same-org dep; likely used in test/config context. | ai | |
| phantom-deps | phantom-dep:@peerbit/pubsub-interface | AI (phantom-deps): Same-org dep; likely used in test/config context. | ai | |
| phantom-deps | phantom-dep:@peerbit/stream-interface | AI (phantom-deps): Same-org dep; likely used in test/config context. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Logging dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:libp2p | AI (phantom-deps): Peer/type dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:pidusage | AI (phantom-deps): Utility dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:libsodium-wrappers | AI (phantom-deps): Crypto dep referenced in config; stable false positive. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 6.1.1 | 22 / 8 | |
| 6.1.0 | 22 / 8 | |
| 6.0.35 | 22 / 7 | |
| 6.0.34 | 22 / 7 | |
| 6.0.33 | 22 / 7 | |
| 6.0.32 | 22 / 7 | |
| 6.0.31 | 22 / 7 | |
| 6.0.30 | 22 / 7 | |
| 6.0.29 | 22 / 7 | |
| 6.0.28 | 22 / 7 | |
| 6.0.27 | 22 / 7 | |
| 6.0.26 | 22 / 7 | |
| 6.0.25 | 22 / 7 | |
| 6.0.24 | 22 / 7 | |
| 6.0.23 | 22 / 7 | |
| 6.0.22 | 22 / 7 | |
| 6.0.21 | 22 / 7 | |
| 6.0.20 | 22 / 7 | |
| 6.0.19 | 22 / 7 | |
| 6.0.18 | 22 / 7 | |
| 6.0.17 | 22 / 7 | |
| 6.0.16 | 22 / 7 | |
| 6.0.15 | 22 / 7 | |
| 6.0.14 | 22 / 7 | |
| 6.0.13 | 22 / 7 | |
| 6.0.12 | 22 / 7 | |
| 6.0.11 | 22 / 7 | |
| 6.0.10 | 22 / 7 | |
| 6.0.9 | 22 / 7 | |
| 6.0.8 | 22 / 7 | |
| 6.0.7 | 22 / 7 | |
| 6.0.6 | 22 / 7 | |
| 6.0.5 | 22 / 7 | |
| 6.0.4 | 22 / 7 | |
| 6.0.3 | 22 / 7 | |
| 6.0.2 | 22 / 7 | |
| 6.0.0 | 22 / 7 | |
| 5.0.10 | 22 / 7 | |
| 5.0.9 | 22 / 7 | |
| 5.0.8 | 22 / 7 | |
| 5.0.7 | 22 / 7 | |
| 5.0.6 | 22 / 7 | |
| 5.0.5 | 22 / 7 | |
| 5.0.4 | 22 / 7 | |
| 5.0.3 | 22 / 7 | |
| 5.0.2 | 22 / 7 | |
| 5.0.1 | 22 / 7 | |
| 5.0.0 | 22 / 7 | |
| 4.2.8 | 22 / 7 | |
| 4.2.7 | 22 / 7 | |
| 4.2.6 | 22 / 7 |
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.