@ikas/storefront
Storefront functionality for ikas storefront themes.
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): High-velocity monorepo with automated CI; rapid publishes are the norm for this package across 1947 versions. | ai | |
| source-diff | obfuscated-file:build/components/page/widgets/loyaltyWidget.js | AI (source-diff): Rollup-bundled output with readable imports and business logic; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:build/components/checkout/components/svg/star-loyalty.js | AI (source-diff): Minified SVG React component; purely presentational, no malicious code. | ai | |
| source-diff | obfuscated-file:build/components/page/widgets/popupWidget.js | AI (source-diff): Rollup-bundled output for popup widget feature; no malicious patterns. | ai | |
| dependencies | unvetted-dep:@ikas/popup-script-injector | AI (dependencies): Same-org (@ikas) internal dependency; consistent with the package's established ecosystem pattern. | ai | |
| dependencies | unvetted-dep:@ikas/popup-renderer | AI (dependencies): First-party @ikas ecosystem dependency; consistent with the package's established publishing pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established ikas org package with 1930 versions; lack of Sigstore provenance is consistent across all prior releases. | ai | |
| phantom-deps | phantom-dep:swiper | AI (phantom-deps): Bundled/externalized via rollup; declared as runtime dep but resolved at build time, not directly imported. | ai | |
| phantom-deps | phantom-dep:@ikas/popup-script-injector | AI (phantom-deps): Same-org package; likely used indirectly or via re-export pattern within the ikas monorepo. | ai | |
| phantom-deps | phantom-dep:web-streams-polyfill | AI (phantom-deps): Polyfill referenced in rollup config; not directly imported in source but legitimately bundled. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 5.0.78 | 4 / 36 | |
| 5.0.72 | 4 / 36 | |
| 5.0.69 | 4 / 36 | |
| 5.0.68 | 4 / 36 | |
| 5.0.62 | 4 / 36 | |
| 5.0.56 | 2 / 36 | |
| 5.0.55 | 2 / 36 | |
| 5.0.54 | 2 / 36 | |
| 4.15.85 | 5 / 36 | |
| 4.15.82 | 5 / 36 | |
| 4.15.80 | 5 / 36 | |
| 4.15.65 | 3 / 36 | |
| 4.15.64 | 3 / 36 |
v5.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.68
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.62
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.