@everymatrix/casino-calendar
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/CasinoCalendar-B5QE3h71.js | AI (source-diff): Standard Vite/Rollup minified build output with hashed filename; expected for this Stencil component package. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendarDailyItem-qDeFbIRp.js | AI (source-diff): Standard Vite/Rollup minified build output with hashed filename; expected for this Stencil component package. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendarDailyItem-9BbCkh75.js | AI (source-diff): Standard Vite/Rollup minified build output with hashed filename; expected for this Stencil component package. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendar-B8hV-3Z8.js | AI (source-diff): Standard Vite/Rollup minified build output with hashed filename; expected for this Stencil component package. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendarDailyItem-CVc0yK2I.cjs | AI (source-diff): Standard Rollup/Vite minified build output for a Svelte component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendar-DHlLBasL.cjs | AI (source-diff): Standard Rollup/Vite minified build output for a Svelte component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendarDailyDetails-BdoD5JS8.cjs | AI (source-diff): Standard Rollup/Vite minified build output for a Svelte component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendar-w-wmyyK2.js | AI (source-diff): Standard Rollup/Vite minified build output for a Svelte component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendar-wCj8_Knd.js | AI (source-diff): Standard Rollup/Vite minified build output for a Svelte component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendarDailyItem-D2g-iDX2.js | AI (source-diff): Standard Rollup/Vite minified build output for a Svelte component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendarDailyItem-Dsw3r5ZU.js | AI (source-diff): Standard Rollup/Vite minified build output for a Svelte component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendarDailyItem-DxkzLy2S.js | AI (source-diff): Minified component chunk importing from sibling bundle; normal build output for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendar-aeS7m5XC.js | AI (source-diff): Standard minified Svelte/Stencil bundle output; consistent with package's established build artifact pattern. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendarDailyItem-BttCrDo7.js | AI (source-diff): Minified component chunk importing from sibling bundle; normal build output for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoCalendar-BChhokfs.js | AI (source-diff): Standard minified Svelte/Stencil bundle output; consistent with package's established build artifact pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern for this internal component package across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal component library; no repo/description/deps is consistent across all 584 versions. | ai |
Versions (showing 100 of 417)
| Version | Deps | Published |
|---|---|---|
| 1.74.8 | 0 / 0 | |
| 1.74.7 | 0 / 0 | |
| 1.74.6 | 0 / 0 | |
| 1.74.5 | 0 / 0 | |
| 1.74.4 | 0 / 0 | |
| 1.74.3 | 0 / 0 | |
| 1.74.2 | 0 / 0 | |
| 1.74.1 | 0 / 0 | |
| 1.74.0 | 0 / 0 | |
| 1.73.2 | 0 / 0 | |
| 1.73.1 | 0 / 0 | |
| 1.73.0 | 0 / 0 | |
| 1.72.2 | 0 / 0 | |
| 1.72.1 | 0 / 0 | |
| 1.72.0 | 0 / 0 | |
| 1.71.1 | 0 / 0 | |
| 1.71.0 | 0 / 0 | |
| 1.70.1 | 0 / 0 | |
| 1.70.0 | 0 / 0 | |
| 1.69.3 | 0 / 0 | |
| 1.69.2 | 0 / 0 | |
| 1.69.0 | 0 / 0 | |
| 1.68.0 | 0 / 0 | |
| 1.67.3 | 0 / 0 | |
| 1.67.0 | 0 / 0 | |
| 1.66.2 | 0 / 0 | |
| 1.66.1 | 0 / 0 | |
| 1.66.0 | 0 / 0 | |
| 1.65.3 | 0 / 0 | |
| 1.65.2 | 0 / 0 | |
| 1.65.1 | 0 / 0 | |
| 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.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.54.0 | 2 / 0 | |
| 1.53.12 | 0 / 0 | |
| 1.53.11 | 0 / 0 | |
| 1.53.10 | 0 / 0 | |
| 1.53.0 | 2 / 0 | |
| 1.52.6 | 2 / 0 | |
| 1.52.5 | 2 / 0 | |
| 1.52.4 | 2 / 0 | |
| 1.52.3 | 2 / 0 | |
| 1.52.2 | 2 / 0 | |
| 1.52.1 | 2 / 0 | |
| 1.52.0 | 2 / 0 | |
| 1.51.0 | 2 / 0 | |
| 1.50.1 | 2 / 0 | |
| 1.50.0 | 2 / 0 | |
| 1.49.2 | 2 / 0 | |
| 1.49.1 | 2 / 0 | |
| 1.49.0 | 2 / 0 | |
| 1.48.2 | 2 / 0 | |
| 1.48.1 | 2 / 0 | |
| 1.48.0 | 2 / 0 | |
| 1.47.3 | 2 / 0 | |
| 1.47.2 | 2 / 0 | |
| 1.47.1 | 2 / 0 | |
| 1.47.0 | 2 / 0 | |
| 1.46.1 | 2 / 0 | |
| 1.46.0 | 2 / 0 |
v1.65.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.54.0
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.
v1.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.