graphile-upload-plugin
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): Established publisher; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 51 of 110)
| Version | Deps | Published |
|---|---|---|
| 2.18.0 | 0 / 2 | |
| 2.15.2 | 0 / 2 | |
| 2.14.0 | 0 / 2 | |
| 2.13.1 | 0 / 2 | |
| 2.13.0 | 0 / 2 | |
| 2.12.2 | 0 / 2 | |
| 2.12.1 | 0 / 2 | |
| 2.12.0 | 0 / 2 | |
| 2.11.2 | 0 / 2 | |
| 2.11.1 | 0 / 2 | |
| 2.11.0 | 0 / 2 | |
| 2.10.1 | 0 / 2 | |
| 2.10.0 | 0 / 2 | |
| 2.9.0 | 0 / 2 | |
| 2.8.0 | 0 / 2 | |
| 2.7.0 | 0 / 2 | |
| 2.6.0 | 0 / 2 | |
| 2.5.2 | 0 / 2 | |
| 2.5.1 | 0 / 2 | |
| 2.5.0 | 0 / 2 | |
| 2.4.4 | 0 / 2 | |
| 2.4.3 | 0 / 2 | |
| 2.4.2 | 0 / 2 | |
| 2.2.2 | 0 / 2 | |
| 2.2.1 | 0 / 2 | |
| 2.2.0 | 0 / 2 | |
| 1.1.1 | 5 / 9 | |
| 1.1.0 | 5 / 9 | |
| 1.0.4 | 5 / 9 | |
| 1.0.3 | 5 / 9 | |
| 1.0.2 | 5 / 9 | |
| 1.0.1 | 5 / 9 | |
| 1.0.0 | 5 / 9 | |
| 0.10.4 | 5 / 9 | |
| 0.10.3 | 5 / 9 | |
| 0.10.2 | 5 / 9 | |
| 0.10.1 | 5 / 9 | |
| 0.10.0 | 5 / 9 | |
| 0.9.1 | 5 / 9 | |
| 0.9.0 | 5 / 9 | |
| 0.8.16 | 5 / 9 | |
| 0.8.15 | 5 / 9 | |
| 0.8.14 | 5 / 9 | |
| 0.8.13 | 5 / 9 | |
| 0.8.12 | 5 / 9 | |
| 0.8.11 | 5 / 9 | |
| 0.8.10 | 5 / 9 | |
| 0.8.9 | 5 / 9 | |
| 0.8.8 | 5 / 9 | |
| 0.8.7 | 5 / 9 | |
| 0.8.6 | 5 / 9 |
v2.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.