@justeattakeaway/pie-toast
PIE Design System Toast built using Web Components
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@justeattakeaway/pie-webc-core | AI (dependencies): First-party JustEatTakeaway monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-icons-webc | AI (dependencies): First-party JustEatTakeaway monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-icon-button | AI (dependencies): First-party JustEatTakeaway monorepo dependency; stable pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established JET design system package; provenance absence is consistent across all versions of this monorepo. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 0.13.1 | 4 / 3 | |
| 0.13.0 | 4 / 3 | |
| 0.12.44 | 4 / 3 | |
| 0.12.43 | 4 / 3 | |
| 0.12.42 | 4 / 3 | |
| 0.12.41 | 4 / 3 | |
| 0.12.40 | 4 / 3 | |
| 0.12.39 | 4 / 5 | |
| 0.12.38 | 4 / 5 | |
| 0.12.37 | 4 / 5 | |
| 0.12.36 | 4 / 5 | |
| 0.12.35 | 4 / 5 | |
| 0.12.34 | 4 / 5 | |
| 0.12.33 | 4 / 5 | |
| 0.12.32 | 4 / 5 | |
| 0.12.31 | 4 / 5 | |
| 0.12.30 | 4 / 5 | |
| 0.12.29 | 4 / 5 | |
| 0.12.28 | 4 / 5 | |
| 0.12.27 | 4 / 5 | |
| 0.12.26 | 4 / 5 | |
| 0.12.25 | 4 / 5 | |
| 0.12.24 | 4 / 5 | |
| 0.12.23 | 4 / 5 | |
| 0.12.22 | 4 / 5 | |
| 0.12.21 | 4 / 5 | |
| 0.12.20 | 4 / 5 | |
| 0.12.19 | 4 / 5 | |
| 0.12.18 | 4 / 5 | |
| 0.12.17 | 4 / 5 | |
| 0.12.16 | 4 / 5 | |
| 0.12.15 | 4 / 5 | |
| 0.12.14 | 4 / 5 | |
| 0.12.13 | 4 / 5 | |
| 0.12.12 | 4 / 5 | |
| 0.12.11 | 4 / 5 | |
| 0.12.10 | 4 / 5 | |
| 0.12.9 | 4 / 5 | |
| 0.12.8 | 4 / 5 | |
| 0.12.7 | 4 / 5 | |
| 0.12.6 | 4 / 5 | |
| 0.12.5 | 4 / 5 | |
| 0.12.4 | 4 / 5 | |
| 0.12.3 | 4 / 5 | |
| 0.12.2 | 4 / 5 | |
| 0.12.1 | 4 / 5 | |
| 0.12.0 | 4 / 5 | |
| 0.11.1 | 4 / 5 | |
| 0.11.0 | 4 / 5 | |
| 0.10.2 | 4 / 5 | |
| 0.10.1 | 4 / 5 |
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.14
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.12.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.