@justeattakeaway/pie-thumbnail
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): Consistent across all versions of this org's packages; not a risk signal here. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.8.35 | 1 / 3 | |
| 0.8.34 | 1 / 3 | |
| 0.8.33 | 1 / 3 | |
| 0.8.32 | 1 / 3 | |
| 0.8.31 | 1 / 3 | |
| 0.8.30 | 1 / 3 | |
| 0.8.29 | 1 / 3 | |
| 0.8.28 | 1 / 3 | |
| 0.8.27 | 1 / 3 | |
| 0.8.26 | 1 / 5 | |
| 0.8.25 | 1 / 5 | |
| 0.8.24 | 1 / 5 | |
| 0.8.23 | 1 / 5 | |
| 0.8.22 | 1 / 5 | |
| 0.8.21 | 1 / 5 | |
| 0.8.20 | 1 / 5 | |
| 0.8.19 | 1 / 5 | |
| 0.8.18 | 1 / 5 | |
| 0.8.17 | 1 / 5 | |
| 0.8.16 | 1 / 5 | |
| 0.8.15 | 1 / 5 | |
| 0.8.14 | 1 / 5 | |
| 0.8.13 | 1 / 5 | |
| 0.8.12 | 1 / 5 | |
| 0.8.11 | 1 / 5 | |
| 0.8.10 | 1 / 5 | |
| 0.8.9 | 1 / 5 | |
| 0.8.8 | 1 / 5 | |
| 0.8.7 | 1 / 5 | |
| 0.8.6 | 1 / 5 | |
| 0.8.5 | 1 / 5 | |
| 0.8.4 | 1 / 5 | |
| 0.8.3 | 1 / 5 | |
| 0.8.2 | 1 / 5 | |
| 0.8.1 | 1 / 5 | |
| 0.8.0 | 1 / 5 | |
| 0.7.1 | 1 / 5 | |
| 0.7.0 | 1 / 5 | |
| 0.6.3 | 1 / 4 | |
| 0.6.2 | 1 / 4 | |
| 0.6.1 | 1 / 4 | |
| 0.6.0 | 1 / 4 | |
| 0.5.0 | 1 / 4 | |
| 0.4.0 | 1 / 4 | |
| 0.3.0 | 1 / 4 | |
| 0.2.0 | 1 / 4 | |
| 0.1.0 | 1 / 4 |
v0.8.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.