@justeattakeaway/pie-list
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Monorepo placeholder version used consistently across JustEat pie-* packages, not a malware signal. | ai | |
| source-diff | obfuscated-file:dist/index-KnN5fPmj.js | AI (source-diff): Vite/Lit build bundle, long lines are minification not obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @lit/context is official Lit package matching new context usage. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all JustEatTakeaway PIE packages; org-level publishing pattern, not a per-version concern. | ai | |
| dependencies | unvetted-dep:@justeattakeaway/pie-webc-core | AI (dependencies): Internal JustEatTakeaway monorepo dependency; stable pattern across all PIE component versions. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 2 / 3 | |
| 0.1.1 | 1 / 3 | |
| 0.1.0 | 1 / 3 | |
| 0.0.31 | 1 / 3 | |
| 0.0.30 | 1 / 3 | |
| 0.0.29 | 1 / 3 | |
| 0.0.28 | 1 / 3 | |
| 0.0.27 | 1 / 3 | |
| 0.0.26 | 1 / 3 | |
| 0.0.25 | 1 / 5 | |
| 0.0.24 | 1 / 5 | |
| 0.0.23 | 1 / 5 | |
| 0.0.22 | 1 / 5 | |
| 0.0.21 | 1 / 5 | |
| 0.0.20 | 1 / 5 | |
| 0.0.19 | 1 / 5 | |
| 0.0.18 | 1 / 5 | |
| 0.0.17 | 1 / 5 | |
| 0.0.16 | 1 / 5 | |
| 0.0.15 | 1 / 5 | |
| 0.0.14 | 1 / 5 | |
| 0.0.13 | 1 / 5 | |
| 0.0.12 | 1 / 5 | |
| 0.0.11 | 1 / 5 | |
| 0.0.10 | 1 / 5 | |
| 0.0.9 | 1 / 5 | |
| 0.0.8 | 1 / 5 | |
| 0.0.7 | 1 / 5 | |
| 0.0.6 | 1 / 5 | |
| 0.0.5 | 1 / 5 | |
| 0.0.4 | 1 / 5 | |
| 0.0.3 | 1 / 5 | |
| 0.0.2 | 1 / 5 | |
| 0.0.1 | 1 / 5 | |
| 0.0.0 | 1 / 5 |
v0.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.