@peerbit/document-proxy
RPC/proxy adapter for @peerbit/document (canonical runtime)
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@peerbit/program | AI (phantom-deps): Same-org dependency; phantom-dep heuristic false positive for this package's proxy pattern. | ai |
Versions (showing 51 of 67)
| Version | Deps | Published |
|---|---|---|
| 2.0.60 | 10 / 1 | |
| 2.0.59 | 10 / 1 | |
| 2.0.58 | 10 / 1 | |
| 2.0.57 | 10 / 1 | |
| 2.0.56 | 10 / 1 | |
| 2.0.55 | 10 / 1 | |
| 2.0.54 | 10 / 1 | |
| 2.0.53 | 10 / 1 | |
| 2.0.52 | 10 / 1 | |
| 2.0.51 | 10 / 1 | |
| 2.0.50 | 10 / 1 | |
| 2.0.49 | 10 / 1 | |
| 2.0.48 | 10 / 1 | |
| 2.0.47 | 10 / 1 | |
| 2.0.46 | 10 / 1 | |
| 2.0.45 | 10 / 1 | |
| 2.0.44 | 10 / 1 | |
| 2.0.43 | 10 / 1 | |
| 2.0.42 | 10 / 1 | |
| 2.0.41 | 10 / 1 | |
| 2.0.40 | 10 / 1 | |
| 2.0.39 | 10 / 1 | |
| 2.0.38 | 10 / 1 | |
| 2.0.37 | 10 / 1 | |
| 2.0.36 | 10 / 1 | |
| 2.0.35 | 10 / 1 | |
| 2.0.34 | 10 / 1 | |
| 2.0.33 | 10 / 1 | |
| 2.0.32 | 10 / 1 | |
| 2.0.31 | 10 / 1 | |
| 2.0.30 | 10 / 1 | |
| 2.0.29 | 10 / 1 | |
| 2.0.28 | 10 / 1 | |
| 2.0.27 | 10 / 1 | |
| 2.0.26 | 10 / 1 | |
| 2.0.25 | 10 / 1 | |
| 2.0.24 | 10 / 1 | |
| 2.0.23 | 10 / 1 | |
| 2.0.22 | 10 / 1 | |
| 2.0.21 | 10 / 1 | |
| 2.0.20 | 10 / 1 | |
| 2.0.19 | 10 / 1 | |
| 2.0.18 | 10 / 1 | |
| 2.0.17 | 10 / 1 | |
| 2.0.16 | 10 / 1 | |
| 2.0.15 | 10 / 1 | |
| 2.0.14 | 10 / 1 | |
| 2.0.13 | 10 / 1 | |
| 2.0.12 | 10 / 1 | |
| 2.0.11 | 10 / 1 | |
| 2.0.10 | 10 / 1 |
v2.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.