@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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/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/casino-challenges-overlay/casino-challenges-overlay-e43b403e.js | AI (source-diff): Standard Stencil.js minified build output. | 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-75a7cbc9.js | AI (source-diff): Minified Stencil bundle; content is component logic, no exfiltration or shell patterns. | 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-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/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/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/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/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-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/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/cjs/casino-challenges-overlay-be7f1691.js | AI (source-diff): Standard Stencil.js CJS minified bundle; no malicious patterns. | 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/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/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-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/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-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/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/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-5fcad42a.js | AI (source-diff): Standard Stencil minified build output; consistent pattern across all versions of this 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/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 51 of 100)
| Version | Deps | Published |
|---|---|---|
| 0.17.30 | 0 / 0 | |
| 0.17.29 | 0 / 0 | |
| 0.17.28 | 0 / 0 | |
| 0.17.27 | 0 / 0 | |
| 0.17.26 | 0 / 0 | |
| 0.17.25 | 0 / 0 | |
| 0.17.24 | 0 / 0 | |
| 0.17.23 | 0 / 0 | |
| 0.17.22 | 0 / 0 | |
| 0.17.21 | 0 / 0 | |
| 0.17.20 | 0 / 0 | |
| 0.17.19 | 0 / 0 | |
| 0.17.18 | 0 / 0 | |
| 0.17.17 | 0 / 0 | |
| 0.17.16 | 0 / 0 | |
| 0.17.15 | 0 / 0 | |
| 0.17.9 | 0 / 0 | |
| 0.17.8 | 0 / 0 | |
| 0.17.7 | 0 / 0 | |
| 0.17.6 | 0 / 0 | |
| 0.17.5 | 0 / 0 | |
| 0.17.4 | 0 / 0 | |
| 0.17.3 | 0 / 0 | |
| 0.17.2 | 0 / 0 | |
| 0.17.1 | 0 / 0 | |
| 0.17.0 | 0 / 0 | |
| 0.16.15 | 0 / 0 | |
| 0.16.14 | 0 / 0 | |
| 0.16.13 | 0 / 0 | |
| 0.16.12 | 0 / 0 | |
| 0.16.11 | 0 / 0 | |
| 0.16.10 | 0 / 0 | |
| 0.16.9 | 0 / 0 | |
| 0.16.8 | 0 / 0 | |
| 0.16.7 | 0 / 0 | |
| 0.16.6 | 0 / 0 | |
| 0.16.5 | 0 / 0 | |
| 0.16.4 | 0 / 0 | |
| 0.16.3 | 0 / 0 | |
| 0.16.2 | 0 / 0 | |
| 0.16.1 | 0 / 0 | |
| 0.16.0 | 0 / 0 | |
| 0.15.8 | 0 / 0 | |
| 0.15.7 | 0 / 0 | |
| 0.15.6 | 0 / 0 | |
| 0.15.5 | 0 / 0 | |
| 0.15.4 | 0 / 0 | |
| 0.15.3 | 0 / 0 | |
| 0.15.2 | 0 / 0 | |
| 0.15.1 | 0 / 0 | |
| 0.15.0 | 0 / 0 |
v0.17.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (goe.suta) than the most recent previously approved version (adrian.pripon) on 2026-05-26, but goe.suta is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.6
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.15
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.14
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.13
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.12
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.11
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.10
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.9
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.