@everymatrix/casino-challenges-overlay
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-5e111f1c.js | AI (source-diff): Bundled ESM build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-43a19d97.js | AI (source-diff): Bundled build output with readable comments, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-5e111f1c.js | AI (source-diff): Bundled Stencil/Rollup build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-5413414e.js | AI (source-diff): Standard Rollup minified bundle output for this Stencil widget package; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-e44d1628.js | AI (source-diff): CJS build artifact; same pattern as ESM counterpart, stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-5413414e.js | AI (source-diff): ESM build artifact with readable JSDoc comments; long-line heuristic false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-e43b403e.js | AI (source-diff): Standard Stencil.js minified build output. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/index-7fdd1cbf.js | AI (source-diff): Standard Stencil.js runtime bundle; consistent with established @everymatrix widget pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-e43b403e.js | AI (source-diff): Standard Stencil.js minified build output. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-a75f839f.js | AI (source-diff): Standard Stencil.js minified build output. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-ac229a05.js | AI (source-diff): CJS counterpart of the same Stencil build; readable structure with JSDoc comments. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-75a7cbc9.js | AI (source-diff): Minified Stencil bundle; content is component logic, no exfiltration or shell patterns. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-75a7cbc9.js | AI (source-diff): Standard Stencil.js minified build output; ESM variant includes readable JSDoc, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-eef46bdb.js | AI (source-diff): Standard Stencil.js minified build output; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-2332b012.js | AI (source-diff): Standard Stencil.js minified build output; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay_2.entry.js | AI (source-diff): Standard Stencil.js minified build output; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay_2.entry.js | AI (source-diff): Standard Stencil.js minified build output; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay_2.cjs.entry.js | AI (source-diff): Standard Stencil.js minified build output; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/index-2be35f12.js | AI (source-diff): Standard Stencil.js runtime bundle; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-eef46bdb.js | AI (source-diff): Standard Stencil.js minified build output; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-48b07cb1.js | AI (source-diff): Standard Rollup/Stencil minified build output for this widget package; consistent across all versions. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-48b07cb1.js | AI (source-diff): Standard Rollup/Stencil minified build output for this widget package; consistent across all versions. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-3f42bf67.js | AI (source-diff): Standard Rollup/Stencil minified build output for this widget package; consistent across all versions. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-f1ed1c93.js | AI (source-diff): Standard Stencil.js CJS minified bundle; no malicious patterns, readable source comments present. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-78a3b5f9.js | AI (source-diff): Standard Stencil.js minified bundle output; consistent with @everymatrix widget build pattern. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-78a3b5f9.js | AI (source-diff): Standard Stencil.js ESM minified bundle; no malicious patterns, readable source comments present. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-89a5469f.js | AI (source-diff): Minified widget bundle consistent with Stencil build pipeline used across this package family. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-77be149d.js | AI (source-diff): Standard Rollup/Stencil CJS bundle output; long lines are minified widget code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-89a5469f.js | AI (source-diff): Standard Rollup/Stencil ESM bundle output; same pattern as other @everymatrix widget packages. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-e801be58.js | AI (source-diff): Standard Rollup/Stencil minified build output; consistent with this widget package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/index-4cb6ae8e.js | AI (source-diff): Standard Stencil runtime bundle; minification pattern matches known Stencil output. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-e801be58.js | AI (source-diff): Standard Rollup/Stencil minified build output; consistent with this widget package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-3f4dc422.js | AI (source-diff): Standard Rollup/Stencil minified build output; consistent with this widget package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-68684fef.js | AI (source-diff): Standard Stencil.js ESM minified bundle; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-be7f1691.js | AI (source-diff): Standard Stencil.js CJS minified bundle; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-68684fef.js | AI (source-diff): Standard Stencil.js minified bundle; consistent with all prior @everymatrix package builds. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-9bb4cca8.js | AI (source-diff): Standard minified Stencil build bundle; pattern is stable across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-9bb4cca8.js | AI (source-diff): Standard minified Stencil build bundle; pattern is stable across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-4b5f57a1.js | AI (source-diff): Standard minified Stencil build bundle; pattern is stable across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-a5ae48f5.js | AI (source-diff): Standard Stencil.js minified ESM build artifact; consistent with package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/index-be60b13e.js | AI (source-diff): Stencil.js runtime bundle (minified); consistent with package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-a5ae48f5.js | AI (source-diff): Standard Stencil.js minified bundle; consistent with package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-68ec1eb8.js | AI (source-diff): Standard Stencil.js minified build artifact; pattern is consistent across all versions of this widget package. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-5fcad42a.js | AI (source-diff): Standard Stencil minified build output; consistent pattern across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-5fcad42a.js | AI (source-diff): Standard Stencil minified build output; consistent pattern across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-365b73b3.js | AI (source-diff): Standard Stencil minified build output; consistent pattern across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-6f01489c.js | AI (source-diff): Standard Rollup/Stencil minified bundle output; consistent with this package's build pattern across all versions. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-fd6ae571.js | AI (source-diff): Standard Rollup/Stencil minified bundle output; consistent with this package's build pattern across all versions. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-fd6ae571.js | AI (source-diff): Standard Rollup/Stencil minified bundle output; consistent with this package's build pattern across all versions. | ai | |
| source-diff | obfuscated-file:dist/casino-challenges-overlay/casino-challenges-overlay-0ab4098a.js | AI (source-diff): Standard Stencil.js minified bundle output; consistent pattern across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/cjs/casino-challenges-overlay-9b3b30da.js | AI (source-diff): Readable CJS build artifact with comments; not obfuscated, just long lines from bundling. | ai | |
| source-diff | obfuscated-file:dist/esm/casino-challenges-overlay-0ab4098a.js | AI (source-diff): Readable ESM build artifact with comments; not obfuscated, just long lines from bundling. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org widget package; no deps/description/keywords is normal for this component library pattern across 220 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this org's widget packages; not a malice indicator here. | ai |
Versions (showing 100 of 299)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 0.10.10 | 0 / 0 | |
| 0.10.9 | 0 / 0 | |
| 0.10.8 | 0 / 0 | |
| 0.10.7 | 0 / 0 | |
| 0.10.6 | 0 / 0 | |
| 0.10.5 | 0 / 0 | |
| 0.10.4 | 0 / 0 | |
| 0.10.3 | 0 / 0 | |
| 0.10.2 | 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.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.
v0.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.