@everymatrix/casino-games-category-section-nd
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:components/CasinoGamesCategorySectionNd-Ujun8cK8.js | AI (source-diff): Standard bundled ESM build output; stable for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-BzgjblK2.cjs | AI (source-diff): Standard bundled CJS build output with i18n strings; stable for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-6iNq5ImS.js | AI (source-diff): Standard bundled ESM build output; stable for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-BSLqNPhu.js | AI (source-diff): ESM variant of thumbnail component; standard build output. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Multiple build targets (CJS+ESM+esnext) produce many files per version; normal for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-C6crjCJr.js | AI (source-diff): ESM variant of sort component; standard build output. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-BV3Ui5_3.js | AI (source-diff): ESM variant of sort component; standard build output. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-Ct_UV4Yl.js | AI (source-diff): ESM variant of thumbnail component; standard build output. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-mWdCfGLM.js | AI (source-diff): ESM variant of main component bundle; standard build output. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-BkE_6984.js | AI (source-diff): ESM variant of main component bundle; standard build output. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-SLFszfcy.js | AI (source-diff): ESM variant of CasinoFilter bundle; standard build output. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-BmzSQuiz.js | AI (source-diff): ESM variant of CasinoFilter bundle; standard build output. | ai | |
| source-diff | obfuscated-file:stencil/ui-image_2-ZFidgTXM.cjs | AI (source-diff): Stencil UI image component with skeleton CSS; standard build output. | ai | |
| source-diff | obfuscated-file:stencil/index-97d17652-ILzgTtTR.cjs | AI (source-diff): Stencil runtime bundle; standard web component framework output. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-D_l_aKYr.cjs | AI (source-diff): Minified Svelte sort component with i18n; standard build output. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-DgjESuIb.cjs | AI (source-diff): Minified component bundle with date-fns helpers; standard build output. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-CMM25Znw.cjs | AI (source-diff): Minified Svelte component bundle; i18n strings visible, no suspicious payload. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-Dcqa8XDU.cjs | AI (source-diff): Minified Svelte component bundle output; standard for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-AER2vIg2.js | AI (source-diff): Standard Svelte/Stencil minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-CQ-kukn3.js | AI (source-diff): Standard Svelte/Stencil minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-DMfzqMqk.js | AI (source-diff): Standard Svelte/Stencil minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-DnLmaF2F.js | AI (source-diff): Standard Svelte/Stencil minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-UjrLK27j.js | AI (source-diff): Standard Svelte/Stencil minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-DMYh5GKZ.js | AI (source-diff): Standard Svelte/Stencil minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-C_oEaOdj.js | AI (source-diff): Standard Svelte/Stencil minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-C6Psb7D3.js | AI (source-diff): Standard Svelte/Stencil minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-GwnqOBrv.js | AI (source-diff): Standard Svelte/Vite minified bundle output for this casino UI component package. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-CnEKVAtB.cjs | AI (source-diff): Standard Svelte/Vite minified bundle output for this casino UI component package. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-cuDYIs62.cjs | AI (source-diff): Standard Svelte/Vite minified bundle output for this casino UI component package. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-C-DwBmrL.js | AI (source-diff): Standard Svelte/Vite minified bundle output for this casino UI component package. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-DNt3bPWO.js | AI (source-diff): Standard Svelte/Vite minified bundle output for this casino UI component package. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-ClM3-m05.js | AI (source-diff): Standard Svelte/Vite minified bundle output for this casino UI component package. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-D834sY26.js | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-r0zwIu_o.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-vaBMxojj.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-CLPdqPqm.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-CcT2oc80.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-DLw8LQpc.js | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-kU7KiX_c.js | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-C7Du5Hqa.js | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-CflUckE5.js | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-DbM-MgEC.js | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-MA67cRB7.js | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-uQEzky7p.js | AI (source-diff): Standard Rollup/Vite minified bundle output for Svelte UI component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-kyZEUL_7.cjs | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-qujm3aYx.js | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-Ble7RivW.js | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-DRMyPLUT.js | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-CoA7lek0.js | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-D3Qjbu53.js | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-3PJUXCFi.js | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-Cydm7m2v.js | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-CfmNpR8n.js | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-VNKspKX0.cjs | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-B-XLbllc.cjs | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-C9FDCPn5.cjs | AI (source-diff): Standard Rollup/Vite minified build output for this casino UI component library. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-DMtcIJpO.js | AI (source-diff): Standard Rollup/Vite minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-CoWDVNhC.js | AI (source-diff): Standard Rollup/Vite minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-B22wLyI-.js | AI (source-diff): Standard Rollup/Vite minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-C1EiXmAC.js | AI (source-diff): Standard Rollup/Vite minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoFilter-5M2JC_AV.js | AI (source-diff): Standard Rollup/Vite minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-wykGWqIt.cjs | AI (source-diff): Standard Rollup/Vite minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-Dn607ygR.cjs | AI (source-diff): Standard Rollup/Vite minified build output for this UI component package; consistent across all versions. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-JA8FHBdz.js | AI (source-diff): Standard Rollup/Vite minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoSort-C4BlpoVe.js | AI (source-diff): Standard Rollup/Vite minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-DXcO927H.js | AI (source-diff): Standard Rollup/Vite minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-Dd4YoZTQ.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this UI component package; consistent with all prior versions. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-BYWOnARh.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this UI component package; consistent with all prior versions. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-D0QecLeO.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for this UI component package; consistent with all prior versions. | ai | |
| source-diff | obfuscated-file:components/CasinoGamesCategorySectionNd-B00IN0NY.cjs | AI (source-diff): Standard Rollup/Vite minified bundle output for this UI component package; consistent with all prior versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped enterprise UI component package; no description/repo/keywords is normal for internal distribution packages in this namespace. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-CAChQj_f.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this UI component package; consistent with all prior versions. | ai | |
| source-diff | obfuscated-file:components/CasinoGameThumbnailNd-BkzX6gmH.js | AI (source-diff): Standard Rollup/Vite minified bundle output for this UI component package; consistent with all prior versions. | ai |
Versions (showing 51 of 222)
| Version | Deps | Published |
|---|---|---|
| 1.94.32 | 0 / 0 | |
| 1.94.31 | 0 / 0 | |
| 1.94.30 | 0 / 0 | |
| 1.94.29 | 0 / 0 | |
| 1.94.28 | 0 / 0 | |
| 1.94.27 | 0 / 0 | |
| 1.94.26 | 0 / 0 | |
| 1.94.25 | 0 / 0 | |
| 1.94.24 | 0 / 0 | |
| 1.94.23 | 0 / 0 | |
| 1.94.22 | 0 / 0 | |
| 1.94.21 | 0 / 0 | |
| 1.94.20 | 0 / 0 | |
| 1.94.19 | 0 / 0 | |
| 1.94.18 | 0 / 0 | |
| 1.94.17 | 0 / 0 | |
| 1.94.16 | 0 / 0 | |
| 1.94.15 | 0 / 0 | |
| 1.94.9 | 0 / 0 | |
| 1.94.8 | 0 / 0 | |
| 1.94.7 | 0 / 0 | |
| 1.94.6 | 0 / 0 | |
| 1.94.5 | 0 / 0 | |
| 1.94.4 | 0 / 0 | |
| 1.94.3 | 0 / 0 | |
| 1.94.2 | 0 / 0 | |
| 1.94.1 | 0 / 0 | |
| 1.94.0 | 0 / 0 | |
| 1.93.15 | 0 / 0 | |
| 1.93.14 | 0 / 0 | |
| 1.93.13 | 0 / 0 | |
| 1.93.12 | 0 / 0 | |
| 1.93.11 | 0 / 0 | |
| 1.93.10 | 0 / 0 | |
| 1.93.9 | 0 / 0 | |
| 1.93.8 | 0 / 0 | |
| 1.93.7 | 0 / 0 | |
| 1.93.6 | 0 / 0 | |
| 1.93.5 | 0 / 0 | |
| 1.93.4 | 0 / 0 | |
| 1.93.3 | 0 / 0 | |
| 1.93.2 | 0 / 0 | |
| 1.93.1 | 0 / 0 | |
| 1.93.0 | 0 / 0 | |
| 1.92.8 | 0 / 0 | |
| 1.92.7 | 0 / 0 | |
| 1.92.6 | 0 / 0 | |
| 1.92.5 | 0 / 0 | |
| 1.92.4 | 0 / 0 | |
| 1.92.3 | 0 / 0 | |
| 1.92.2 | 0 / 0 |
v1.94.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.20
10 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.
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.
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.
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.
This version was published by a different npm account (goe.suta) than the most recent previously approved version (adrian.pripon) on 2026-05-29, 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.
v1.94.19
10 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.
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.
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.
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.
This version was published by a different npm account (goe.suta) than the most recent previously approved version (adrian.pripon) on 2026-05-28, 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.
v1.94.18
10 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.
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.
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.
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.
This version was published by a different npm account (goe.suta) than the most recent previously approved version (adrian.pripon) on 2026-05-28, 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.
v1.94.17
10 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.
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.
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.
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.
This version was published by a different npm account (goe.suta) than the most recent previously approved version (adrian.pripon) on 2026-05-27, 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.
v1.94.16
10 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.
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.
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.
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.
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.
v1.94.15
10 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.
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.
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.
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.
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.
v1.94.9
9 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.
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.
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.
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.
v1.94.8
9 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.
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.
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.
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.
v1.94.7
9 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.
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.
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.
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.
v1.94.6
9 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.
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.
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.
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.
v1.94.5
9 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.
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.
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.
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.
v1.94.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.3
13 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.
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.
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.
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.
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.
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.
v1.94.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.1
13 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.
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.
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.
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.
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.
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.
v1.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.15
13 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.
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.
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.
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.
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.
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.
v1.93.14
13 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.
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.
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.
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.
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.
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.
v1.93.13
13 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.
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.
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.
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.
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.
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.
v1.93.12
13 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.
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.
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.
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.
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.
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.
v1.93.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.