@justeattakeaway/pie-spinner
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; consistent publishing pattern across 158 versions without provenance. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.5.2 | 1 / 4 | |
| 1.5.1 | 1 / 4 | |
| 1.5.0 | 1 / 4 | |
| 1.4.19 | 1 / 4 | |
| 1.4.18 | 1 / 4 | |
| 1.4.17 | 1 / 4 | |
| 1.4.16 | 1 / 4 | |
| 1.4.15 | 1 / 4 | |
| 1.4.14 | 1 / 4 | |
| 1.4.13 | 1 / 6 | |
| 1.4.12 | 1 / 6 | |
| 1.4.11 | 1 / 6 | |
| 1.4.10 | 1 / 6 | |
| 1.4.9 | 1 / 6 | |
| 1.4.8 | 1 / 6 | |
| 1.4.7 | 1 / 6 | |
| 1.4.6 | 1 / 6 | |
| 1.4.5 | 1 / 6 | |
| 1.4.4 | 1 / 6 | |
| 1.4.3 | 1 / 6 | |
| 1.4.2 | 1 / 6 | |
| 1.4.1 | 1 / 6 | |
| 1.4.0 | 1 / 6 | |
| 1.3.7 | 1 / 6 | |
| 1.3.6 | 1 / 6 | |
| 1.3.5 | 1 / 6 | |
| 1.3.4 | 1 / 6 | |
| 1.3.3 | 1 / 6 | |
| 1.3.2 | 1 / 6 | |
| 1.3.1 | 1 / 6 | |
| 1.3.0 | 1 / 6 | |
| 1.2.5 | 1 / 6 | |
| 1.2.4 | 1 / 6 | |
| 1.2.3 | 1 / 6 | |
| 1.2.2 | 1 / 6 | |
| 1.2.1 | 1 / 6 | |
| 1.2.0 | 1 / 6 | |
| 1.1.1 | 1 / 6 | |
| 1.1.0 | 1 / 6 | |
| 1.0.1 | 1 / 5 | |
| 1.0.0 | 1 / 5 |
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.