@everymatrix/casino-page
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 | no-description | AI (npm-metadata): Long-standing pattern for this internal component package. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendar-feWE0Y4B.cjs | AI (source-diff): Bundled Vite/Svelte output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoPage-D_LgcMWE.js | AI (source-diff): Bundled build output (Vite chunk), not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoPage-lhLJyvKO.js | AI (source-diff): Bundled build output (Vite chunk), not obfuscation. | ai | |
| phantom-deps | phantom-dep:@everymatrix/casino-jackpot-banner | AI (phantom-deps): Same-org monorepo pattern; stable across versions. | ai | |
| phantom-deps | phantom-dep:@everymatrix/casino-random-game | AI (phantom-deps): Same-org monorepo pattern; stable across versions. | ai | |
| phantom-deps | phantom-dep:@everymatrix/casino-my-games | AI (phantom-deps): Same-org monorepo pattern; stable across versions. | ai | |
| phantom-deps | phantom-dep:@everymatrix/casino-calendar | AI (phantom-deps): Same-org monorepo pattern; stable across versions. | ai | |
| phantom-deps | phantom-dep:@everymatrix/casino-search | AI (phantom-deps): Same-org monorepo pattern; stable across versions. | ai | |
| phantom-deps | phantom-dep:@everymatrix/casino-winners | AI (phantom-deps): Same-org monorepo pattern; stable across versions. | ai | |
| phantom-deps | phantom-dep:@everymatrix/casino-games-category-section | AI (phantom-deps): Same-org monorepo pattern; stable across versions. | ai | |
| phantom-deps | phantom-dep:@everymatrix/casino-collections-providers | AI (phantom-deps): Same-org monorepo pattern; stable across versions. | ai | |
| phantom-deps | phantom-dep:@everymatrix/casino-play-random-game | AI (phantom-deps): Same-org monorepo pattern; stable across versions. | ai | |
| phantom-deps | phantom-dep:sirv-cli | AI (phantom-deps): Used in npm 'start' script, not source import. | ai | |
| phantom-deps | phantom-dep:svelte | AI (phantom-deps): Framework used via config/build, not direct import. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): Used in build scripts only. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySection-CYAVM0Ug.cjs | AI (source-diff): Bundled build output, not obfuscation; matches package's normal component chunking. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Routine maintainer roster change within established org monorepo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer roster change within established org monorepo. | ai | |
| source-diff | obfuscated-file:components/CasinoPage-eCv6pYb2.cjs | AI (source-diff): Minified bundled component output, not true obfuscation; consistent with package's build pipeline. | ai | |
| source-diff | obfuscated-file:components/CasinoPage-ByrxRamE.cjs | AI (source-diff): Bundled Svelte/stencil build output, not true obfuscation; consistent with package's build pipeline. | ai | |
| source-diff | obfuscated-file:components/CasinoPage-SKT1W7KF.cjs | AI (source-diff): Bundled Svelte/Stencil component output, not true obfuscation; matches package's build tooling. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Metadata sparsity typical of internal monorepo component packages, not spam. | ai | |
| source-diff | obfuscated-file:stencil/casino-play-random-game_2-cZvlv_fo.cjs | AI (source-diff): Minified Stencil component output; no malicious patterns, consistent with package's build artifacts. | ai | |
| source-diff | obfuscated-file:components/CasinoPage-CDakhIvY.cjs | AI (source-diff): Standard minified bundle; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnail-Bcw2baBS.cjs | AI (source-diff): Standard minified bundle; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendar-C42gDFHO.cjs | AI (source-diff): Standard minified Svelte bundle output; consistent with this package's build pattern across all versions. | ai | |
| source-diff | obfuscated-file:stencil/casino-play-random-game_2-CCCLDakd.cjs | AI (source-diff): Minified Stencil component bundle; no malicious indicators in samples. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendar-4k288rHh.cjs | AI (source-diff): Minified Svelte bundle output; consistent with this package's established build pattern. | ai | |
| source-diff | large-new-source-files | AI (source-diff): High file count is normal for this package's bundled component releases across 1007 versions. | ai | |
| provenance | publisher-changed | AI (provenance): New publisher adrian.pripon is an established org account with 12k+ approvals; consistent with internal maintainer rotation for @everymatrix packages. | ai |
Versions (showing 100 of 688)
| Version | Deps | Published |
|---|---|---|
| 1.90.34 | 0 / 0 | |
| 1.90.33 | 0 / 0 | |
| 1.90.32 | 0 / 0 | |
| 1.90.31 | 0 / 0 | |
| 1.90.30 | 0 / 0 | |
| 1.90.29 | 0 / 0 | |
| 1.90.28 | 0 / 0 | |
| 1.90.27 | 0 / 0 | |
| 1.90.26 | 0 / 0 | |
| 1.90.25 | 0 / 0 | |
| 1.90.24 | 0 / 0 | |
| 1.90.23 | 0 / 0 | |
| 1.90.22 | 0 / 0 | |
| 1.90.21 | 0 / 0 | |
| 1.90.20 | 0 / 0 | |
| 1.90.19 | 0 / 0 | |
| 1.90.18 | 0 / 0 | |
| 1.90.17 | 0 / 0 | |
| 1.90.16 | 0 / 0 | |
| 1.90.10 | 0 / 0 | |
| 1.90.9 | 0 / 0 | |
| 1.90.8 | 0 / 0 | |
| 1.90.7 | 0 / 0 | |
| 1.90.6 | 0 / 0 | |
| 1.90.5 | 0 / 0 | |
| 1.90.4 | 0 / 0 | |
| 1.90.3 | 0 / 0 | |
| 1.90.2 | 0 / 0 | |
| 1.90.1 | 0 / 0 | |
| 1.90.0 | 0 / 0 | |
| 1.89.3 | 0 / 0 | |
| 1.89.2 | 0 / 0 | |
| 1.89.1 | 0 / 0 | |
| 1.89.0 | 0 / 0 | |
| 1.88.24 | 0 / 0 | |
| 1.88.23 | 0 / 0 | |
| 1.88.22 | 0 / 0 | |
| 1.88.21 | 0 / 0 | |
| 1.88.20 | 0 / 0 | |
| 1.88.19 | 0 / 0 | |
| 1.88.18 | 0 / 0 | |
| 1.88.17 | 0 / 0 | |
| 1.88.16 | 0 / 0 | |
| 1.88.15 | 0 / 0 | |
| 1.88.14 | 0 / 0 | |
| 1.88.13 | 0 / 0 | |
| 1.88.12 | 0 / 0 | |
| 1.88.11 | 0 / 0 | |
| 1.88.10 | 0 / 0 | |
| 1.88.9 | 0 / 0 | |
| 1.88.8 | 0 / 0 | |
| 1.88.7 | 0 / 0 | |
| 1.88.6 | 0 / 0 | |
| 1.88.5 | 0 / 0 | |
| 1.88.4 | 0 / 0 | |
| 1.88.3 | 0 / 0 | |
| 1.88.2 | 0 / 0 | |
| 1.88.1 | 0 / 0 | |
| 1.88.0 | 0 / 0 | |
| 1.87.44 | 0 / 0 | |
| 1.87.43 | 0 / 0 | |
| 1.87.42 | 0 / 0 | |
| 1.87.41 | 0 / 0 | |
| 1.87.40 | 0 / 0 | |
| 1.87.39 | 0 / 0 | |
| 1.87.38 | 0 / 0 | |
| 1.87.37 | 0 / 0 | |
| 1.87.36 | 0 / 0 | |
| 1.87.35 | 0 / 0 | |
| 1.87.34 | 0 / 0 | |
| 1.87.33 | 0 / 0 | |
| 1.87.32 | 0 / 0 | |
| 1.87.31 | 0 / 0 | |
| 1.87.30 | 0 / 0 | |
| 1.87.29 | 0 / 0 | |
| 1.87.28 | 0 / 0 | |
| 1.87.27 | 0 / 0 | |
| 1.87.26 | 0 / 0 | |
| 1.87.25 | 0 / 0 | |
| 1.87.24 | 0 / 0 | |
| 1.87.23 | 0 / 0 | |
| 1.87.22 | 0 / 0 | |
| 1.87.21 | 0 / 0 | |
| 1.87.20 | 0 / 0 | |
| 1.87.19 | 0 / 0 | |
| 1.87.18 | 0 / 0 | |
| 1.87.17 | 0 / 0 | |
| 1.87.16 | 0 / 0 | |
| 1.87.15 | 0 / 0 | |
| 1.87.14 | 0 / 0 | |
| 1.87.13 | 0 / 0 | |
| 1.87.12 | 0 / 0 | |
| 1.87.11 | 0 / 0 | |
| 1.87.10 | 0 / 0 | |
| 1.87.9 | 0 / 0 | |
| 1.87.8 | 0 / 0 | |
| 1.87.7 | 0 / 0 | |
| 1.87.6 | 0 / 0 | |
| 1.87.5 | 0 / 0 | |
| 1.87.4 | 0 / 0 |
v1.90.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.89.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.89.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.89.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.