@everymatrix/casino-footer-v2
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:components/CasinoFooterV2-cCV6vQ69.js | AI (source-diff): Standard minified Svelte/framework bundle output; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:components/CasinoFooterV2-DzgHz_2X.js | AI (source-diff): Standard minified Svelte/framework bundle output; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerPanicButton-CT4QRCzL.cjs | AI (source-diff): Bundled CJS component with i18n strings; stable for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoFooterThumbnail-Cqz-oCSI.js | AI (source-diff): ESM variant of thumbnail bundle; stable for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoFooterThumbnail-DuvSIZSj.js | AI (source-diff): ESM variant of thumbnail bundle; stable for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoFooterV2-C7QV1csP.js | AI (source-diff): ESM entry bundle with custom elements registration; stable for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoFooterV2-CQ0xH-7N.js | AI (source-diff): ESM entry bundle variant; stable for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoFooterSection-DIk5Ne4a.cjs | AI (source-diff): Standard Rollup/Vite CJS bundle output for Svelte component; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoFooterThumbnail-C3CgssYK.cjs | AI (source-diff): Bundled CJS output with Microsoft TS helpers; stable for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoFooterV2-pJVDiGaw.cjs | AI (source-diff): Bundled CJS entry with moment.js and custom elements; stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org component library; no public repo/keywords/deps is normal for this package's publishing pattern. | ai | |
| source-diff | obfuscated-file:components/CasinoFooterV2-Dw6BVPa2.js | AI (source-diff): Standard minified Svelte/JS bundle output; consistent with this package's component library pattern across 807 versions. | ai | |
| source-diff | obfuscated-file:components/CasinoFooterV2-B4P6AAJY.js | AI (source-diff): Standard minified Svelte/JS bundle output; consistent with this package's component library pattern across 807 versions. | ai | |
| provenance | publisher-changed | AI (provenance): New publisher adrian.pripon is an established org account with 11k+ approved packages; consistent with internal team rotation. | ai |
Versions (showing 46 of 347)
| Version | Deps | Published |
|---|---|---|
| 1.65.0 | 0 / 0 | |
| 1.64.8 | 0 / 0 | |
| 1.64.7 | 0 / 0 | |
| 1.64.6 | 0 / 0 | |
| 1.64.5 | 0 / 0 | |
| 1.64.4 | 0 / 0 | |
| 1.64.2 | 0 / 0 | |
| 1.64.1 | 0 / 0 | |
| 1.64.0 | 0 / 0 | |
| 1.63.3 | 0 / 0 | |
| 1.63.2 | 0 / 0 | |
| 1.63.1 | 0 / 0 | |
| 1.63.0 | 0 / 0 | |
| 1.62.4 | 0 / 0 | |
| 1.62.3 | 0 / 0 | |
| 1.62.2 | 0 / 0 | |
| 1.62.1 | 0 / 0 | |
| 1.62.0 | 0 / 0 | |
| 1.61.1 | 0 / 0 | |
| 1.61.0 | 0 / 0 | |
| 1.60.2 | 0 / 0 | |
| 1.60.1 | 0 / 0 | |
| 1.60.0 | 0 / 0 | |
| 1.59.3 | 0 / 0 | |
| 1.59.2 | 0 / 0 | |
| 1.59.1 | 0 / 0 | |
| 1.59.0 | 0 / 0 | |
| 1.58.1 | 0 / 0 | |
| 1.58.0 | 0 / 0 | |
| 1.57.0 | 0 / 0 | |
| 1.56.3 | 0 / 0 | |
| 1.56.2 | 0 / 0 | |
| 1.56.0 | 0 / 0 | |
| 1.55.1 | 0 / 0 | |
| 1.55.0 | 0 / 0 | |
| 1.54.12 | 0 / 0 | |
| 1.54.11 | 0 / 0 | |
| 1.54.10 | 0 / 0 | |
| 1.54.9 | 0 / 0 | |
| 1.54.8 | 0 / 0 | |
| 1.54.6 | 0 / 0 | |
| 1.54.4 | 0 / 0 | |
| 1.54.2 | 0 / 0 | |
| 1.53.12 | 0 / 0 | |
| 1.53.11 | 0 / 0 | |
| 1.53.10 | 0 / 0 |
v1.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.