@everymatrix/casino-collections-providers
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/CasinoCollectionsProviders-DCRxx5hj.cjs | AI (source-diff): Standard minified Rollup/Vite build output for a Svelte component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoCollectionsProviders-C2nfp2G6.js | AI (source-diff): Standard minified Rollup/Vite build output for a Svelte component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoCollectionsProviders-DVkj2YC8.js | AI (source-diff): Standard minified Rollup/Vite build output for a Svelte component; no malicious patterns. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped component package; missing metadata is a stable characteristic, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal package; no description is consistent across all 638 versions. | ai | |
| provenance | no-provenance | AI (provenance): No provenance has been a stable characteristic of this package across its history. | ai |
Versions (showing 11 of 413)
| Version | Deps | Published |
|---|---|---|
| 1.31.0 | 3 / 15 | |
| 1.30.1 | 3 / 15 | |
| 1.30.0 | 3 / 15 | |
| 1.29.9 | 3 / 15 | |
| 1.29.8 | 3 / 15 | |
| 1.29.7 | 3 / 15 | |
| 1.29.6 | 3 / 15 | |
| 1.0.72 | 0 / 0 | |
| 1.0.71 | 0 / 0 | |
| 1.0.70 | 0 / 0 | |
| 1.0.69 | 0 / 0 |
v1.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.