@gershy/disk
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): No provenance is common (~88% of npm); no other risk signals present for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.0.33 | 1 / 1 | |
| 0.0.32 | 1 / 1 | |
| 0.0.31 | 1 / 1 | |
| 0.0.30 | 1 / 1 | |
| 0.0.29 | 1 / 1 | |
| 0.0.28 | 1 / 1 | |
| 0.0.27 | 1 / 1 | |
| 0.0.19 | 1 / 1 | |
| 0.0.18 | 1 / 1 | |
| 0.0.17 | 1 / 1 | |
| 0.0.16 | 1 / 1 | |
| 0.0.15 | 1 / 1 | |
| 0.0.14 | 1 / 1 | |
| 0.0.13 | 1 / 3 | |
| 0.0.12 | 1 / 3 | |
| 0.0.11 | 1 / 3 | |
| 0.0.10 | 1 / 3 | |
| 0.0.9 | 1 / 3 | |
| 0.0.8 | 1 / 3 | |
| 0.0.6 | 1 / 3 | |
| 0.0.2 | 1 / 3 | |
| 0.0.1 | 1 / 3 |
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.