@justeattakeaway/pie-form-label
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 JustEatTakeaway org package; lack of provenance is consistent across all their releases. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 0.18.30 | 1 / 6 | |
| 0.18.29 | 1 / 6 | |
| 0.18.28 | 1 / 6 | |
| 0.18.27 | 1 / 6 | |
| 0.18.26 | 1 / 6 | |
| 0.18.25 | 1 / 6 | |
| 0.18.24 | 1 / 6 | |
| 0.18.23 | 1 / 6 | |
| 0.18.22 | 1 / 8 | |
| 0.18.21 | 1 / 8 | |
| 0.18.20 | 1 / 8 | |
| 0.18.19 | 1 / 8 | |
| 0.18.18 | 1 / 8 | |
| 0.18.17 | 1 / 8 | |
| 0.18.16 | 1 / 8 | |
| 0.18.15 | 1 / 8 | |
| 0.18.14 | 1 / 8 | |
| 0.18.13 | 1 / 8 | |
| 0.18.12 | 1 / 8 | |
| 0.18.11 | 1 / 8 | |
| 0.18.10 | 1 / 8 | |
| 0.18.9 | 1 / 8 | |
| 0.18.8 | 1 / 8 | |
| 0.18.7 | 1 / 8 | |
| 0.18.6 | 1 / 8 | |
| 0.18.5 | 1 / 8 | |
| 0.18.4 | 1 / 8 | |
| 0.18.3 | 1 / 8 | |
| 0.18.2 | 1 / 8 | |
| 0.18.1 | 1 / 8 | |
| 0.18.0 | 1 / 8 | |
| 0.17.0 | 1 / 8 | |
| 0.16.4 | 1 / 8 | |
| 0.16.3 | 1 / 8 | |
| 0.16.2 | 1 / 8 | |
| 0.16.1 | 1 / 8 | |
| 0.16.0 | 1 / 8 | |
| 0.15.1 | 1 / 8 | |
| 0.15.0 | 1 / 8 | |
| 0.14.5 | 1 / 7 | |
| 0.14.4 | 1 / 7 | |
| 0.14.3 | 1 / 7 | |
| 0.14.2 | 1 / 7 | |
| 0.14.1 | 1 / 7 | |
| 0.14.0 | 1 / 6 | |
| 0.13.6 | 1 / 6 | |
| 0.13.5 | 1 / 6 | |
| 0.13.4 | 1 / 6 |
v0.18.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.