@peerbit/canonical-host
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all peerbit monorepo packages; not a risk signal for this publisher. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 1.0.53 | 5 / 1 | |
| 1.0.52 | 5 / 1 | |
| 1.0.51 | 5 / 1 | |
| 1.0.50 | 5 / 1 | |
| 1.0.49 | 5 / 1 | |
| 1.0.48 | 5 / 1 | |
| 1.0.47 | 5 / 1 | |
| 1.0.46 | 5 / 1 | |
| 1.0.45 | 5 / 1 | |
| 1.0.44 | 5 / 1 | |
| 1.0.43 | 5 / 1 | |
| 1.0.42 | 5 / 1 | |
| 1.0.41 | 5 / 1 | |
| 1.0.40 | 5 / 1 | |
| 1.0.39 | 5 / 1 | |
| 1.0.38 | 5 / 1 | |
| 1.0.37 | 5 / 1 | |
| 1.0.36 | 5 / 1 | |
| 1.0.35 | 5 / 1 | |
| 1.0.34 | 5 / 1 | |
| 1.0.33 | 5 / 1 | |
| 1.0.32 | 5 / 1 | |
| 1.0.31 | 5 / 1 | |
| 1.0.30 | 5 / 1 | |
| 1.0.29 | 5 / 1 | |
| 1.0.28 | 5 / 1 | |
| 1.0.27 | 5 / 1 | |
| 1.0.26 | 5 / 1 | |
| 1.0.25 | 5 / 1 | |
| 1.0.24 | 5 / 1 | |
| 1.0.23 | 5 / 1 | |
| 1.0.22 | 5 / 1 | |
| 1.0.21 | 5 / 1 | |
| 1.0.20 | 5 / 1 | |
| 1.0.19 | 5 / 1 | |
| 1.0.18 | 5 / 1 | |
| 1.0.17 | 5 / 1 | |
| 1.0.16 | 5 / 1 | |
| 1.0.15 | 5 / 1 | |
| 1.0.14 | 5 / 1 | |
| 1.0.13 | 5 / 1 | |
| 1.0.12 | 5 / 1 | |
| 1.0.11 | 5 / 1 | |
| 1.0.10 | 5 / 1 | |
| 1.0.9 | 5 / 1 | |
| 1.0.8 | 5 / 1 | |
| 1.0.7 | 5 / 1 | |
| 1.0.5 | 5 / 1 | |
| 1.0.4 | 5 / 1 | |
| 1.0.3 | 5 / 1 | |
| 1.0.2 | 5 / 1 |
v1.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.