@justeattakeaway/pie-webc
Component bundle containing all PIE 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, 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@justeattakeaway/pie-input | AI (dependencies): First-party sibling package from same org/monorepo, not a third-party unvetted dep. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-icon-with-background | AI (dependencies): First-party sibling component from same monorepo/publisher. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Expected addition of a first-party sibling package within the design system. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-link | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-list | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-tabs | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-radio | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-avatar | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-select | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-switch | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-divider | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-tag | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-checkbox | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-textarea | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-thumbnail | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-breadcrumb | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-data-table | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-form-label | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-text-input | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-icon-button | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-spinner | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-card | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-chip | AI (dependencies): First-party JET PIE component; stable pattern for this aggregator package. | ai |
Versions (showing 100 of 225)
| Version | Deps | Published |
|---|---|---|
| 0.7.3 | 28 / 2 | |
| 0.7.2 | 28 / 2 | |
| 0.7.1 | 28 / 2 | |
| 0.7.0 | 28 / 2 | |
| 0.6.45 | 27 / 2 | |
| 0.6.44 | 27 / 2 | |
| 0.6.43 | 27 / 2 | |
| 0.6.42 | 27 / 2 | |
| 0.6.41 | 27 / 2 | |
| 0.6.40 | 27 / 2 | |
| 0.6.39 | 27 / 2 | |
| 0.6.38 | 27 / 2 | |
| 0.6.37 | 27 / 2 | |
| 0.6.36 | 27 / 2 | |
| 0.6.35 | 27 / 2 | |
| 0.6.34 | 27 / 2 | |
| 0.6.33 | 27 / 2 | |
| 0.6.32 | 27 / 2 | |
| 0.6.31 | 27 / 2 | |
| 0.6.30 | 27 / 2 | |
| 0.6.29 | 26 / 2 | |
| 0.6.28 | 26 / 2 | |
| 0.6.27 | 26 / 2 | |
| 0.6.26 | 26 / 2 | |
| 0.6.25 | 26 / 2 | |
| 0.6.24 | 26 / 2 | |
| 0.6.23 | 25 / 2 | |
| 0.6.22 | 25 / 2 | |
| 0.6.21 | 25 / 2 | |
| 0.6.20 | 25 / 2 | |
| 0.6.19 | 25 / 2 | |
| 0.6.18 | 25 / 2 | |
| 0.6.17 | 25 / 2 | |
| 0.6.16 | 25 / 2 | |
| 0.6.15 | 25 / 2 | |
| 0.6.14 | 25 / 2 | |
| 0.6.13 | 25 / 2 | |
| 0.6.12 | 25 / 2 | |
| 0.6.11 | 25 / 2 | |
| 0.6.10 | 24 / 2 | |
| 0.6.9 | 24 / 2 | |
| 0.6.8 | 24 / 2 | |
| 0.6.7 | 24 / 2 | |
| 0.6.6 | 24 / 2 | |
| 0.6.5 | 24 / 2 | |
| 0.6.4 | 24 / 2 | |
| 0.6.3 | 24 / 2 | |
| 0.6.2 | 24 / 2 | |
| 0.6.1 | 24 / 2 | |
| 0.6.0 | 24 / 2 | |
| 0.5.59 | 24 / 2 | |
| 0.5.58 | 24 / 2 | |
| 0.5.57 | 23 / 2 | |
| 0.5.56 | 23 / 2 | |
| 0.5.55 | 22 / 2 | |
| 0.5.54 | 22 / 2 | |
| 0.5.53 | 22 / 2 | |
| 0.5.52 | 22 / 2 | |
| 0.5.51 | 22 / 2 | |
| 0.5.50 | 22 / 2 | |
| 0.5.49 | 22 / 2 | |
| 0.5.48 | 22 / 2 | |
| 0.5.47 | 22 / 2 | |
| 0.5.46 | 22 / 2 | |
| 0.5.45 | 22 / 2 | |
| 0.5.44 | 22 / 2 | |
| 0.5.43 | 22 / 2 | |
| 0.5.42 | 22 / 2 | |
| 0.5.41 | 22 / 2 | |
| 0.5.40 | 22 / 2 | |
| 0.5.39 | 22 / 2 | |
| 0.5.38 | 22 / 2 | |
| 0.5.37 | 22 / 2 | |
| 0.5.36 | 22 / 2 | |
| 0.5.35 | 22 / 2 | |
| 0.5.34 | 22 / 2 | |
| 0.5.33 | 22 / 2 | |
| 0.5.32 | 22 / 2 | |
| 0.5.31 | 21 / 2 | |
| 0.5.30 | 20 / 2 | |
| 0.5.29 | 19 / 2 | |
| 0.5.28 | 19 / 2 | |
| 0.5.27 | 19 / 2 | |
| 0.5.26 | 19 / 2 | |
| 0.5.25 | 19 / 2 | |
| 0.5.23 | 19 / 2 | |
| 0.5.22 | 19 / 2 | |
| 0.5.21 | 19 / 2 | |
| 0.5.20 | 19 / 2 | |
| 0.5.19 | 19 / 2 | |
| 0.5.18 | 19 / 2 | |
| 0.5.17 | 19 / 2 | |
| 0.5.16 | 19 / 2 | |
| 0.5.15 | 19 / 2 | |
| 0.5.14 | 19 / 2 | |
| 0.5.13 | 19 / 2 | |
| 0.5.12 | 19 / 2 | |
| 0.5.11 | 18 / 2 | |
| 0.5.10 | 18 / 2 | |
| 0.5.9 | 18 / 2 |
v0.6.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.