@peerbit/document-interface
Document store interface
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with long history; provenance not enabled but no other risk signals present. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 5 approved packages; @peerbit ecosystem with 417 versions; no code changes from prior approved version. | ai |
Versions (showing 51 of 71)
| Version | Deps | Published |
|---|---|---|
| 3.2.53 | 4 / 0 | |
| 3.2.52 | 4 / 0 | |
| 3.2.51 | 4 / 0 | |
| 3.2.50 | 4 / 0 | |
| 3.2.49 | 4 / 0 | |
| 3.2.48 | 4 / 0 | |
| 3.2.47 | 4 / 0 | |
| 3.2.46 | 4 / 0 | |
| 3.2.45 | 4 / 0 | |
| 3.2.44 | 4 / 0 | |
| 3.2.43 | 4 / 0 | |
| 3.2.42 | 4 / 0 | |
| 3.2.41 | 4 / 0 | |
| 3.2.40 | 4 / 0 | |
| 3.2.39 | 4 / 0 | |
| 3.2.38 | 4 / 0 | |
| 3.2.37 | 4 / 0 | |
| 3.2.36 | 4 / 0 | |
| 3.2.35 | 4 / 0 | |
| 3.2.34 | 4 / 0 | |
| 3.2.33 | 4 / 0 | |
| 3.2.32 | 4 / 0 | |
| 3.2.31 | 4 / 0 | |
| 3.2.30 | 4 / 0 | |
| 3.2.29 | 4 / 0 | |
| 3.2.28 | 4 / 0 | |
| 3.2.27 | 4 / 0 | |
| 3.2.26 | 4 / 0 | |
| 3.2.25 | 4 / 0 | |
| 3.2.24 | 4 / 0 | |
| 3.2.23 | 4 / 0 | |
| 3.2.22 | 4 / 0 | |
| 3.2.21 | 4 / 0 | |
| 3.2.20 | 4 / 0 | |
| 3.2.19 | 4 / 0 | |
| 3.2.18 | 4 / 0 | |
| 3.2.17 | 4 / 0 | |
| 3.2.16 | 4 / 0 | |
| 3.2.15 | 4 / 0 | |
| 3.2.14 | 4 / 0 | |
| 3.2.13 | 4 / 0 | |
| 3.2.12 | 4 / 0 | |
| 3.2.11 | 4 / 0 | |
| 3.2.10 | 4 / 0 | |
| 3.2.9 | 4 / 0 | |
| 3.2.8 | 4 / 0 | |
| 3.2.7 | 4 / 0 | |
| 3.2.5 | 4 / 0 | |
| 3.2.4 | 4 / 0 | |
| 3.2.3 | 4 / 0 | |
| 3.2.2 | 4 / 0 |
v3.2.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.