@peerbit/document-react
React hooks for @peerbit/document
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@peerbit/react | AI (dependencies): Same-org @peerbit/* dependency; consistent with package purpose across all versions. | ai | |
| dependencies | unvetted-dep:@peerbit/document | AI (dependencies): Same-org @peerbit/* dependency; core dep for this React wrapper package. | ai | |
| dependencies | unvetted-dep:@peerbit/indexer-interface | AI (dependencies): Same-org @peerbit/* dependency; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @peerbit/* releases; not a per-version risk signal for this org. | ai | |
| phantom-deps | phantom-dep:@peerbit/logger | AI (phantom-deps): Same org scope; phantom-dep false positive common in monorepo packages where logger is a transitive/re-exported dep. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 1.0.44 | 5 / 16 | |
| 1.0.43 | 5 / 16 | |
| 1.0.42 | 5 / 16 | |
| 1.0.41 | 5 / 16 | |
| 1.0.40 | 5 / 16 | |
| 1.0.39 | 5 / 16 | |
| 1.0.38 | 5 / 16 | |
| 1.0.37 | 5 / 16 | |
| 1.0.36 | 5 / 16 | |
| 1.0.35 | 5 / 16 | |
| 1.0.34 | 5 / 16 | |
| 1.0.33 | 5 / 16 | |
| 1.0.32 | 5 / 16 | |
| 1.0.31 | 5 / 16 | |
| 1.0.30 | 5 / 16 | |
| 1.0.29 | 5 / 16 | |
| 1.0.28 | 5 / 16 | |
| 1.0.27 | 5 / 16 | |
| 1.0.26 | 5 / 16 | |
| 0.4.10 | 5 / 13 | |
| 0.4.1 | 5 / 13 | |
| 0.4.0 | 5 / 13 | |
| 0.3.1 | 5 / 13 | |
| 0.3.0 | 5 / 13 | |
| 0.2.0 | 5 / 13 | |
| 0.1.4 | 5 / 13 | |
| 0.1.3 | 5 / 13 | |
| 0.1.2 | 5 / 13 | |
| 0.1.1 | 5 / 13 | |
| 0.1.0 | 5 / 13 |
v1.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marcus.pousette.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.