@everymatrix/casino-challenges-overlay-modal
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:dist/esm/casino-challenges-overlay-modal-8bfd3fa4.js | AI (source-diff): ESM bundle of same source; readable, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-modal-21242c31.js | AI (source-diff): CJS bundle of same source; readable, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/casino-challenges-overlay-modal-8bfd3fa4.js | AI (source-diff): Bundled Stencil/Rollup output, not obfuscation; stable across versions of this widget. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/casino-challenges-overlay-modal-db247915.js | AI (source-diff): Standard Stencil.js minified build output; ESM counterpart shows identical benign widget code with full comments. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-modal-dc6a3d2b.js | AI (source-diff): CJS build output from Stencil compiler; content matches the readable ESM source. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-modal-db247915.js | AI (source-diff): Readable ESM build of the same widget; minification is expected for this package. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/casino-challenges-overlay-modal-c6c434fc.js | AI (source-diff): Standard Stencil.js minified build output; consistent with this package's established release pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-modal-c6c434fc.js | AI (source-diff): Standard Stencil.js minified build output; consistent with this package's established release pattern. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-modal-9c6d5914.js | AI (source-diff): Standard Stencil.js minified build output; consistent with this package's established release pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-modal-c2779f9d.js | AI (source-diff): Readable ESM build with full JSDoc; minification is normal for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/index-f13cfc58.js | AI (source-diff): Stencil runtime bundle; minified but consistent with the framework's known output pattern. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-modal-f175177e.js | AI (source-diff): CJS build output matching the ESM source; standard Stencil.js artifact. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/casino-challenges-overlay-modal-c2779f9d.js | AI (source-diff): Standard Stencil.js minified build output; readable ESM counterpart confirms benign UI widget code. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/casino-challenges-overlay-modal-e822a04e.js | AI (source-diff): Standard Rollup/Stencil minified bundle output; consistent pattern across all @everymatrix widget packages. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-modal-51feec57.js | AI (source-diff): Standard Rollup/Stencil minified bundle output; consistent pattern across all @everymatrix widget packages. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-modal-e822a04e.js | AI (source-diff): Standard Rollup/Stencil minified bundle output; consistent pattern across all @everymatrix widget packages. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-modal-fab551cf.js | AI (source-diff): Readable commented CJS build artifact, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-modal-d2385e9a.js | AI (source-diff): Readable commented ESM build artifact, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/casino-challenges-overlay-modal-d2385e9a.js | AI (source-diff): Standard minified Stencil build output; ESM/CJS counterparts confirm legitimate readable source. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-modal-12648731.js | AI (source-diff): Standard Rollup/Stencil build output with long bundled lines; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-modal-b880b02b.js | AI (source-diff): Standard Stencil ESM build artifact; readable source with JSDoc comments, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/casino-challenges-overlay-modal-b880b02b.js | AI (source-diff): Standard minified ESM bundle from Stencil build pipeline; content is benign UI component code. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/casino-challenges-overlay-modal-a6da84b6.js | AI (source-diff): Standard Rollup/Stencil minified bundle; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/index-603664b0.js | AI (source-diff): Standard Stencil runtime bundle; minification pattern consistent with legitimate build tooling. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-modal-a6da84b6.js | AI (source-diff): Standard Rollup/Stencil minified bundle; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-modal-5004ed4a.js | AI (source-diff): Standard Rollup/Stencil minified bundle; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-modal-3fbdf2d7.js | AI (source-diff): Standard Rollup CJS bundle output for this Stencil widget; long lines are minified but not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-modal-f5be3740.js | AI (source-diff): Standard Rollup ESM bundle output; same pattern as other @everymatrix widget packages. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay-modal/casino-challenges-overlay-modal-f5be3740.js | AI (source-diff): Standard Stencil IIFE bundle; minified but readable widget code, no malicious patterns. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package with 216 versions; sparse metadata is typical for internal widget components published via Artifactory. | ai |
Versions (showing 100 of 304)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 0 / 0 | |
| 0.14.2 | 0 / 0 | |
| 0.14.1 | 0 / 0 | |
| 0.14.0 | 0 / 0 | |
| 0.13.37 | 0 / 0 | |
| 0.13.36 | 0 / 0 | |
| 0.13.35 | 0 / 0 | |
| 0.13.34 | 0 / 0 | |
| 0.13.33 | 0 / 0 | |
| 0.13.32 | 0 / 0 | |
| 0.13.31 | 0 / 0 | |
| 0.13.30 | 0 / 0 | |
| 0.13.29 | 0 / 0 | |
| 0.13.28 | 0 / 0 | |
| 0.13.27 | 0 / 0 | |
| 0.13.26 | 0 / 0 | |
| 0.13.25 | 0 / 0 | |
| 0.13.24 | 0 / 0 | |
| 0.13.23 | 0 / 0 | |
| 0.13.22 | 0 / 0 | |
| 0.13.21 | 0 / 0 | |
| 0.13.20 | 0 / 0 | |
| 0.13.19 | 0 / 0 | |
| 0.13.18 | 0 / 0 | |
| 0.13.17 | 0 / 0 | |
| 0.13.16 | 0 / 0 | |
| 0.13.10 | 0 / 0 | |
| 0.13.9 | 0 / 0 | |
| 0.13.8 | 0 / 0 | |
| 0.13.7 | 0 / 0 | |
| 0.13.6 | 0 / 0 | |
| 0.13.5 | 0 / 0 | |
| 0.13.4 | 0 / 0 | |
| 0.13.3 | 0 / 0 | |
| 0.13.2 | 0 / 0 | |
| 0.13.1 | 0 / 0 | |
| 0.13.0 | 0 / 0 | |
| 0.12.3 | 0 / 0 | |
| 0.12.2 | 0 / 0 | |
| 0.12.1 | 0 / 0 | |
| 0.12.0 | 0 / 0 | |
| 0.11.24 | 0 / 0 | |
| 0.11.23 | 0 / 0 | |
| 0.11.22 | 0 / 0 | |
| 0.11.21 | 0 / 0 | |
| 0.11.20 | 0 / 0 | |
| 0.11.19 | 0 / 0 | |
| 0.11.18 | 0 / 0 | |
| 0.11.17 | 0 / 0 | |
| 0.11.16 | 0 / 0 | |
| 0.11.15 | 0 / 0 | |
| 0.11.14 | 0 / 0 | |
| 0.11.13 | 0 / 0 | |
| 0.11.12 | 0 / 0 | |
| 0.11.11 | 0 / 0 | |
| 0.11.10 | 0 / 0 | |
| 0.11.9 | 0 / 0 | |
| 0.11.8 | 0 / 0 | |
| 0.11.7 | 0 / 0 | |
| 0.11.6 | 0 / 0 | |
| 0.11.5 | 0 / 0 | |
| 0.11.4 | 0 / 0 | |
| 0.11.3 | 0 / 0 | |
| 0.11.2 | 0 / 0 | |
| 0.11.1 | 0 / 0 | |
| 0.11.0 | 0 / 0 | |
| 0.10.44 | 0 / 0 | |
| 0.10.43 | 0 / 0 | |
| 0.10.42 | 0 / 0 | |
| 0.10.41 | 0 / 0 | |
| 0.10.40 | 0 / 0 | |
| 0.10.39 | 0 / 0 | |
| 0.10.38 | 0 / 0 | |
| 0.10.37 | 0 / 0 | |
| 0.10.36 | 0 / 0 | |
| 0.10.35 | 0 / 0 | |
| 0.10.34 | 0 / 0 | |
| 0.10.33 | 0 / 0 | |
| 0.10.32 | 0 / 0 | |
| 0.10.31 | 0 / 0 | |
| 0.10.30 | 0 / 0 | |
| 0.10.29 | 0 / 0 | |
| 0.10.28 | 0 / 0 | |
| 0.10.27 | 0 / 0 | |
| 0.10.26 | 0 / 0 | |
| 0.10.25 | 0 / 0 | |
| 0.10.24 | 0 / 0 | |
| 0.10.23 | 0 / 0 | |
| 0.10.22 | 0 / 0 | |
| 0.10.21 | 0 / 0 | |
| 0.10.20 | 0 / 0 | |
| 0.10.19 | 0 / 0 | |
| 0.10.18 | 0 / 0 | |
| 0.10.17 | 0 / 0 | |
| 0.10.16 | 0 / 0 | |
| 0.10.15 | 0 / 0 | |
| 0.10.14 | 0 / 0 | |
| 0.10.13 | 0 / 0 | |
| 0.10.12 | 0 / 0 | |
| 0.10.11 | 0 / 0 |
v0.13.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.