@justeattakeaway/pie-icons-webc
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/IconPaymentWero.js | AI (source-diff): Minified lit component with long SVG path strings, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/IconReorderRewardsLarge.js | AI (source-diff): Minified lit component with long SVG path strings, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/IconPaymentRegiobank.js | AI (source-diff): Bundled icon component output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/IconPaymentSns.js | AI (source-diff): Bundled icon component output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/IconPaymentNationaleNederlanden.js | AI (source-diff): Bundled icon component output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/IconPaymentRabobank.js | AI (source-diff): Bundled icon component output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/IconPaymentAfterpay.js | AI (source-diff): Minified vite/rollup bundle output, not true obfuscation; no malicious behavior present. | ai | |
| source-diff | obfuscated-file:dist/IconPaymentAlliedIrishBank.js | AI (source-diff): Minified build output for an icon component; benign. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon files as part of normal releases. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-managed bot publisher with strong track record; churn expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org bot publishing pipeline, not a takeover indicator. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 1.27.1 | 1 / 11 | |
| 1.27.0 | 1 / 11 | |
| 1.26.0 | 1 / 11 | |
| 1.25.4 | 1 / 11 | |
| 1.25.3 | 1 / 11 | |
| 1.25.2 | 1 / 11 | |
| 1.25.1 | 1 / 11 | |
| 1.25.0 | 1 / 11 | |
| 1.24.3 | 1 / 11 | |
| 1.24.2 | 1 / 13 | |
| 1.24.1 | 1 / 13 | |
| 1.24.0 | 1 / 13 | |
| 1.23.0 | 1 / 13 | |
| 1.22.0 | 1 / 13 | |
| 1.21.5 | 1 / 13 | |
| 1.21.4 | 1 / 12 | |
| 1.21.3 | 1 / 12 | |
| 1.21.2 | 1 / 12 | |
| 1.21.1 | 1 / 12 | |
| 1.21.0 | 1 / 12 | |
| 1.20.8 | 1 / 12 | |
| 1.20.7 | 1 / 12 | |
| 1.20.6 | 1 / 12 | |
| 1.20.5 | 1 / 12 | |
| 1.20.4 | 1 / 12 | |
| 1.20.3 | 1 / 12 | |
| 1.20.2 | 1 / 12 | |
| 1.20.1 | 1 / 12 | |
| 1.20.0 | 1 / 12 | |
| 1.19.0 | 1 / 12 | |
| 1.18.2 | 1 / 12 | |
| 1.18.1 | 1 / 12 | |
| 1.18.0 | 1 / 12 | |
| 1.17.1 | 1 / 12 | |
| 1.17.0 | 1 / 12 | |
| 1.16.2 | 1 / 12 | |
| 1.13.0 | 1 / 12 | |
| 1.12.0 | 1 / 12 | |
| 1.11.1 | 1 / 12 | |
| 1.11.0 | 1 / 12 | |
| 1.10.1 | 1 / 12 | |
| 1.10.0 | 1 / 12 | |
| 1.9.0 | 1 / 12 | |
| 1.8.0 | 1 / 12 | |
| 1.7.0 | 1 / 12 | |
| 1.6.2 | 1 / 12 | |
| 1.6.1 | 1 / 12 | |
| 1.6.0 | 1 / 12 | |
| 1.5.0 | 1 / 12 | |
| 1.4.0 | 1 / 12 | |
| 1.3.0 | 1 / 12 |
v1.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.