@everymatrix/casino-tournaments-thumbnail-controller
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/CasinoTournamentsThumbnail-D4sDtwt3.js | AI (source-diff): Standard minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-Br1PZvwL.js | AI (source-diff): Standard minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailPrizes-C-CjGpp5.cjs | AI (source-diff): Standard minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailGamesSlider-GhBBqjNv.cjs | AI (source-diff): Standard minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailDuration-DUW_0ATQ.cjs | AI (source-diff): Standard minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-DlT-P3vm.cjs | AI (source-diff): Standard minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-pRt1QJfu.cjs | AI (source-diff): Standard minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-BXm4HvlY.js | AI (source-diff): Standard minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-BDXLt3ay.js | AI (source-diff): Standard minified Svelte component bundle output; stable pattern for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Build output files change hashes each release; expected churn for this package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailGamesSlider-Bcso4CoC.cjs | AI (source-diff): Standard minified build output for this casino widget package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailPrizes-CyeYwLEd.cjs | AI (source-diff): Standard minified build output for this casino widget package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailDuration-D4FD_V96.cjs | AI (source-diff): Standard minified build output for this casino widget package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-CZmpFLLF.cjs | AI (source-diff): Standard minified build output for this casino widget package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-DEMqBHBV.cjs | AI (source-diff): Standard Svelte/Stencil minified build output; readable i18n and component logic visible in samples. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-DT2fNr--.cjs | AI (source-diff): Standard Svelte/Stencil build artifact; readable DOM manipulation code, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-Dl1NPrsB.js | AI (source-diff): Standard Svelte build output; same pattern as sibling files, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-CfdOXwmn.js | AI (source-diff): Standard Svelte build output (ESM format); readable variable names, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailPrizes-DrscwnlQ.cjs | AI (source-diff): Standard Svelte build output; prizes display component, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailGamesSlider-D-Xj1hPU.cjs | AI (source-diff): Standard Svelte build output; UI slider component, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-CWIEcMiG.cjs | AI (source-diff): Standard Svelte build output for this UI component package; minified but not malicious. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailDuration-C1vMpVH3.cjs | AI (source-diff): Standard Svelte build output; i18n strings and CSS, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-BR8vFeoL.js | AI (source-diff): Standard minified Svelte/JS bundle output; consistent with this package's established pattern of shipping compiled components. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-DfF0ST18.js | AI (source-diff): Standard minified Svelte/JS bundle output; consistent with this package's established pattern of shipping compiled components. | ai | |
| source-diff | obfuscated-file:stencil/ui-image_2-ZFidgTXM.cjs | AI (source-diff): Standard minified Stencil UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-CSDNBS1u.cjs | AI (source-diff): Standard minified Svelte build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-B5oA7xOB.cjs | AI (source-diff): Standard minified Svelte/RxJS build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailDuration-BmsYPOji.cjs | AI (source-diff): Standard minified Svelte build output with i18n strings; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailGamesSlider-DsUSEf8W.cjs | AI (source-diff): Standard minified Svelte build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailPrizes-DMD910A-.cjs | AI (source-diff): Standard minified Svelte build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:stencil/index-97d17652-ILzgTtTR.cjs | AI (source-diff): Standard minified Stencil runtime; no malicious patterns. | ai | |
| source-diff | obfuscated-file:stencil/index-b2193545-qC7jkIQW.cjs | AI (source-diff): Standard minified Stencil runtime; no malicious patterns. | ai | |
| source-diff | obfuscated-file:stencil/ui-skeleton-ed169f8f-DiR5y84l.cjs | AI (source-diff): Standard minified Stencil UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-b84P5LC-.js | AI (source-diff): Standard minified Svelte build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-BQPDlD-6.js | AI (source-diff): Standard minified Svelte build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-CHXnZMEK.js | AI (source-diff): Standard minified Svelte build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-Dk5ObYFQ.js | AI (source-diff): Standard minified Svelte build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-DL3dAkta.cjs | AI (source-diff): Standard Svelte/Stencil minified build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-BGZxgi4Q.js | AI (source-diff): Standard Svelte compiled ESM output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-2rFYfEvO.js | AI (source-diff): Standard Svelte compiled ESM output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:stencil/ui-skeleton-ed169f8f-B7StGL8M.cjs | AI (source-diff): Standard Stencil component bundle; no malicious patterns. | ai | |
| source-diff | obfuscated-file:stencil/index-b2193545-BB6id_PQ.cjs | AI (source-diff): Standard Stencil runtime bundle; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailPrizes-a4yxMeyw.cjs | AI (source-diff): Standard minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailGamesSlider-Bh94svG_.cjs | AI (source-diff): Standard minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailDuration-BVQKn_qj.cjs | AI (source-diff): Standard minified build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-oCWe6JMd.cjs | AI (source-diff): Standard minified build output with UI translation strings; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-DD3a1bpc.cjs | AI (source-diff): Standard Svelte/Vite minified build output; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-yXv_8aa_.js | AI (source-diff): Standard Svelte/Vite minified build output; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-DGTv-6Vg.js | AI (source-diff): Standard Svelte/Vite minified build output; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-J7Of-3j4.js | AI (source-diff): Standard Svelte/Vite minified build output; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-Cm8ygS_j.js | AI (source-diff): Standard Svelte/Vite minified build output; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailPrizes-BRbgsA4Y.cjs | AI (source-diff): Standard Svelte/Vite minified build output; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailGamesSlider-HEUEl0MK.cjs | AI (source-diff): Standard Svelte/Vite minified build output; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailDuration-IvKEkgj7.cjs | AI (source-diff): Standard Svelte/Vite minified build output; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnail-DgXXegVa.cjs | AI (source-diff): Standard Svelte/Vite minified build output; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-CJ5s9xEE.js | AI (source-diff): Minified Svelte bundle output; consistent pattern across all versions of this package. | ai | |
| source-diff | obfuscated-file:components/CasinoTournamentsThumbnailController-B9Drlihg.js | AI (source-diff): Minified Svelte bundle output; consistent pattern across all versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern for this org's component packages across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Large org component package; no description/repo/keywords is consistent across all 1021 versions of this package family. | ai |
Versions (showing 100 of 278)
| Version | Deps | Published |
|---|---|---|
| 1.87.6 | 0 / 0 | |
| 1.87.2 | 0 / 0 | |
| 1.87.1 | 0 / 0 | |
| 1.87.0 | 0 / 0 | |
| 1.86.30 | 0 / 0 | |
| 1.86.29 | 0 / 0 | |
| 1.86.28 | 0 / 0 | |
| 1.86.25 | 0 / 0 | |
| 1.86.24 | 0 / 0 | |
| 1.86.23 | 0 / 0 | |
| 1.86.22 | 0 / 0 | |
| 1.86.21 | 0 / 0 | |
| 1.86.20 | 0 / 0 | |
| 1.86.12 | 0 / 0 | |
| 1.86.11 | 0 / 0 | |
| 1.86.10 | 0 / 0 | |
| 1.86.9 | 0 / 0 | |
| 1.86.8 | 0 / 0 | |
| 1.86.7 | 0 / 0 | |
| 1.86.6 | 0 / 0 | |
| 1.86.5 | 0 / 0 | |
| 1.86.4 | 0 / 0 | |
| 1.86.2 | 0 / 0 | |
| 1.86.1 | 0 / 0 | |
| 1.86.0 | 0 / 0 | |
| 1.85.23 | 0 / 0 | |
| 1.85.22 | 0 / 0 | |
| 1.85.21 | 0 / 0 | |
| 1.85.20 | 0 / 0 | |
| 1.85.19 | 0 / 0 | |
| 1.85.18 | 0 / 0 | |
| 1.85.17 | 0 / 0 | |
| 1.85.16 | 0 / 0 | |
| 1.85.15 | 0 / 0 | |
| 1.85.14 | 0 / 0 | |
| 1.85.13 | 0 / 0 | |
| 1.85.12 | 0 / 0 | |
| 1.85.11 | 0 / 0 | |
| 1.85.10 | 0 / 0 | |
| 1.85.9 | 0 / 0 | |
| 1.85.8 | 0 / 0 | |
| 1.85.7 | 0 / 0 | |
| 1.85.6 | 0 / 0 | |
| 1.85.5 | 0 / 0 | |
| 1.85.4 | 0 / 0 | |
| 1.85.3 | 0 / 0 | |
| 1.85.2 | 0 / 0 | |
| 1.85.1 | 0 / 0 | |
| 1.85.0 | 0 / 0 | |
| 1.84.3 | 0 / 0 | |
| 1.84.2 | 0 / 0 | |
| 1.84.1 | 0 / 0 | |
| 1.84.0 | 0 / 0 | |
| 1.83.12 | 0 / 0 | |
| 1.83.11 | 0 / 0 | |
| 1.83.10 | 0 / 0 | |
| 1.83.9 | 0 / 0 | |
| 1.83.8 | 0 / 0 | |
| 1.83.7 | 0 / 0 | |
| 1.83.6 | 0 / 0 | |
| 1.83.5 | 0 / 0 | |
| 1.83.4 | 0 / 0 | |
| 1.83.3 | 0 / 0 | |
| 1.83.2 | 0 / 0 | |
| 1.83.1 | 0 / 0 | |
| 1.83.0 | 0 / 0 | |
| 1.82.0 | 0 / 0 | |
| 1.81.2 | 0 / 0 | |
| 1.81.1 | 0 / 0 | |
| 1.81.0 | 0 / 0 | |
| 1.80.19 | 0 / 0 | |
| 1.80.18 | 0 / 0 | |
| 1.80.17 | 0 / 0 | |
| 1.80.16 | 0 / 0 | |
| 1.80.15 | 0 / 0 | |
| 1.80.14 | 0 / 0 | |
| 1.80.13 | 0 / 0 | |
| 1.80.12 | 0 / 0 | |
| 1.80.11 | 0 / 0 | |
| 1.80.10 | 0 / 0 | |
| 1.80.9 | 0 / 0 | |
| 1.80.8 | 0 / 0 | |
| 1.80.7 | 0 / 0 | |
| 1.80.6 | 0 / 0 | |
| 1.80.5 | 0 / 0 | |
| 1.80.4 | 0 / 0 | |
| 1.80.3 | 0 / 0 | |
| 1.80.2 | 0 / 0 | |
| 1.80.1 | 0 / 0 | |
| 1.80.0 | 0 / 0 | |
| 1.77.32 | 0 / 0 | |
| 1.77.31 | 0 / 0 | |
| 1.77.30 | 0 / 0 | |
| 1.77.29 | 0 / 0 | |
| 1.77.28 | 0 / 0 | |
| 1.77.27 | 0 / 0 | |
| 1.77.26 | 0 / 0 | |
| 1.77.25 | 0 / 0 | |
| 1.77.24 | 0 / 0 | |
| 1.77.23 | 0 / 0 |
v1.87.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.12
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.
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.86.10
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.
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.86.9
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.
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.86.8
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.
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.86.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.86.5
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.
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.86.4
15 findingsThis version was published by a different npm account than previous versions on 2025-12-02. This could indicate a legitimate maintainer transition or an account compromise.
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.
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.86.1
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.
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.86.0
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.
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.85.23
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.
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.85.22
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.
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.85.21
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.
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.85.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.
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.85.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.
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.85.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.12
2 findingsThis version was published by a different npm account than previous versions on 2025-11-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.83.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.83.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.83.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.81.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.81.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.