@justeattakeaway/pie-chip
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 JET Design System package; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 92 of 92)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 3 / 3 | |
| 1.0.6 | 3 / 3 | |
| 1.0.5 | 3 / 3 | |
| 1.0.4 | 3 / 3 | |
| 1.0.3 | 3 / 3 | |
| 1.0.2 | 3 / 3 | |
| 1.0.1 | 3 / 3 | |
| 1.0.0 | 3 / 3 | |
| 0.15.35 | 3 / 3 | |
| 0.15.34 | 3 / 3 | |
| 0.15.33 | 3 / 3 | |
| 0.15.32 | 3 / 3 | |
| 0.15.31 | 3 / 3 | |
| 0.15.30 | 3 / 3 | |
| 0.15.29 | 3 / 3 | |
| 0.15.28 | 3 / 3 | |
| 0.15.27 | 3 / 3 | |
| 0.15.26 | 3 / 3 | |
| 0.15.25 | 3 / 5 | |
| 0.15.24 | 3 / 5 | |
| 0.15.23 | 3 / 5 | |
| 0.15.22 | 3 / 5 | |
| 0.15.21 | 3 / 5 | |
| 0.15.20 | 3 / 5 | |
| 0.15.19 | 3 / 5 | |
| 0.15.18 | 3 / 5 | |
| 0.15.17 | 3 / 5 | |
| 0.15.16 | 3 / 5 | |
| 0.15.15 | 3 / 5 | |
| 0.15.14 | 3 / 5 | |
| 0.15.13 | 3 / 5 | |
| 0.15.12 | 3 / 5 | |
| 0.15.11 | 3 / 5 | |
| 0.15.10 | 3 / 5 | |
| 0.15.9 | 3 / 5 | |
| 0.15.8 | 3 / 5 | |
| 0.15.7 | 3 / 5 | |
| 0.15.6 | 3 / 5 | |
| 0.15.5 | 3 / 5 | |
| 0.15.4 | 3 / 5 | |
| 0.15.3 | 3 / 5 | |
| 0.15.2 | 3 / 5 | |
| 0.15.1 | 3 / 5 | |
| 0.15.0 | 3 / 5 | |
| 0.14.4 | 3 / 5 | |
| 0.14.3 | 3 / 5 | |
| 0.14.2 | 3 / 5 | |
| 0.14.1 | 3 / 5 | |
| 0.14.0 | 3 / 5 | |
| 0.13.0 | 3 / 5 | |
| 0.12.11 | 3 / 5 | |
| 0.12.10 | 3 / 5 | |
| 0.12.9 | 3 / 5 | |
| 0.12.8 | 3 / 5 | |
| 0.12.7 | 3 / 5 | |
| 0.12.6 | 3 / 5 | |
| 0.12.5 | 3 / 5 | |
| 0.12.4 | 3 / 5 | |
| 0.12.3 | 3 / 5 | |
| 0.12.2 | 3 / 5 | |
| 0.12.1 | 3 / 5 | |
| 0.12.0 | 3 / 5 | |
| 0.11.4 | 3 / 5 | |
| 0.11.3 | 3 / 5 | |
| 0.11.2 | 3 / 5 | |
| 0.11.1 | 3 / 5 | |
| 0.11.0 | 3 / 5 | |
| 0.10.2 | 3 / 4 | |
| 0.10.1 | 3 / 4 | |
| 0.10.0 | 3 / 4 | |
| 0.9.7 | 3 / 4 | |
| 0.9.6 | 3 / 4 | |
| 0.9.5 | 3 / 4 | |
| 0.9.4 | 3 / 4 | |
| 0.9.3 | 3 / 4 | |
| 0.9.2 | 3 / 4 | |
| 0.9.1 | 3 / 4 | |
| 0.9.0 | 3 / 4 | |
| 0.8.6 | 3 / 4 | |
| 0.8.5 | 3 / 4 | |
| 0.8.4 | 3 / 4 | |
| 0.8.3 | 3 / 4 | |
| 0.8.2 | 3 / 4 | |
| 0.8.1 | 3 / 4 | |
| 0.8.0 | 3 / 4 | |
| 0.7.2 | 3 / 4 | |
| 0.7.1 | 3 / 3 | |
| 0.7.0 | 3 / 3 | |
| 0.6.4 | 3 / 3 | |
| 0.6.3 | 3 / 3 | |
| 0.6.2 | 3 / 3 | |
| 0.6.1 | 3 / 3 |
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
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.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.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.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.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.
v0.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.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.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.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.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.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.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.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.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.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.
v0.6.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.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.