@everymatrix/player-limit-notification
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/PlayerAccountGamingLimitsPage2Gm16Nd-CYxgOf4l.js | AI (source-diff): Standard Vite ESM build output; contains only UI component logic. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-Cli_k3bu.js | AI (source-diff): Standard Svelte runtime bundle; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-BsVJsyYv.js | AI (source-diff): Standard Svelte runtime bundle; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-DNrNq-BG.js | AI (source-diff): Standard Vite ESM build output; contains only UI component logic. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-Bv_KZvS2.js | AI (source-diff): Standard minified Svelte/Stencil ES module bundle; readable limit config confirms legitimate component. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-DWV868D2.js | AI (source-diff): Standard minified ES module bundle; same pattern as sibling files, legitimate build artifact. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2Nd-BC39vUmO.cjs | AI (source-diff): Standard minified bundle with visible Microsoft TypeScript copyright header; legitimate build artifact. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2Nd-C5NP9M-9.cjs | AI (source-diff): Standard minified Svelte/Stencil bundle output; readable i18n content confirms legitimate component code. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-BXFHqOII.cjs | AI (source-diff): Standard minified Svelte/Stencil bundle output; readable limit-type config confirms legitimate component code. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-CvQlhnPu.js | AI (source-diff): Standard minified Svelte runtime ES module; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-Y644HK5a.js | AI (source-diff): Standard minified Svelte runtime ES module; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-C3PhD9T1.cjs | AI (source-diff): Standard minified Svelte runtime bundle; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-ZbA4YKMr.js | AI (source-diff): Standard minified Svelte/Stencil build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2Nd-D1NAkOSu.cjs | AI (source-diff): Standard minified Svelte/Stencil build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-BQtXaUJG.cjs | AI (source-diff): Standard minified Svelte/Stencil build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2Nd-CTaIpikj.cjs | AI (source-diff): Standard minified Svelte/Stencil build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-DYln6Ff9.js | AI (source-diff): Standard minified Svelte/Stencil build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-DCffPNor.js | AI (source-diff): Standard minified Svelte/Stencil build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-CUM6UV2C.js | AI (source-diff): Standard minified Svelte/Stencil build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-De6UovID.cjs | AI (source-diff): Standard minified Svelte/Stencil build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-zuggJ4lR.js | AI (source-diff): Standard minified Svelte bundle output; no obfuscation, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-DMo7_odP.js | AI (source-diff): Standard minified Svelte bundle output; no obfuscation, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-fgfmAwLi.js | AI (source-diff): Standard minified Svelte bundle output; no obfuscation, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-6jezdPSI.js | AI (source-diff): Standard minified Svelte bundle output; no obfuscation, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2Nd-2z3_GBiO.cjs | AI (source-diff): Standard minified Svelte bundle output; no obfuscation, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-BrMdgJrq.cjs | AI (source-diff): Standard minified Svelte bundle output; no obfuscation, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-DTS6QEQW.cjs | AI (source-diff): Standard minified Svelte bundle output; no obfuscation, no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-OqgKbUVO.js | AI (source-diff): Standard minified Svelte bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2Nd-BPDMvyK7.cjs | AI (source-diff): Standard minified Svelte bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-BH9-r9_l.cjs | AI (source-diff): Standard minified Svelte bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2Nd-BR4RSbJA.cjs | AI (source-diff): Standard minified Svelte bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-T-UYD1v7.cjs | AI (source-diff): Standard minified Svelte bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2Nd-BetTT8pd.js | AI (source-diff): Standard minified Svelte bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2Nd-Rz7KSqHF.js | AI (source-diff): Standard minified Svelte bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-C-0ryr80.js | AI (source-diff): Standard minified Svelte bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-BJ4GfhKT.js | AI (source-diff): Standard minified Svelte bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-EZZH0XKP.js | AI (source-diff): Standard minified Svelte bundle output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-DuwMwZB4.cjs | AI (source-diff): Standard minified Svelte/TS bundle output for this UI component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-Chi9qW1X.js | AI (source-diff): Standard minified Svelte/TS bundle output for this UI component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-DyKrvRVR.js | AI (source-diff): Standard minified Svelte/TS bundle output for this UI component package. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-BUEwj14t.js | AI (source-diff): Standard minified Svelte/TS bundle output for this UI component package. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-DC7uu9Ji.js | AI (source-diff): Standard minified Svelte/TS bundle output for this UI component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2Nd-CDVBLw02.cjs | AI (source-diff): Standard minified Svelte/TS bundle output; includes MS TypeScript copyright header. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-BZYbecUF.cjs | AI (source-diff): Standard minified Svelte/TS bundle output for this UI component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2Nd-3ielBINM.cjs | AI (source-diff): Standard minified Svelte/TS bundle output for this UI component package; consistent across all versions. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-CJxWmBd5.js | AI (source-diff): Minified ES module build artifact; readable limit-type config confirms legitimate compiled output. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-Cw75gubz.js | AI (source-diff): Minified Svelte runtime helpers; standard framework code, no malicious content. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-9BWfVeNT.js | AI (source-diff): Minified Svelte runtime helpers; standard framework code, no malicious content. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-SnnLEGC_.js | AI (source-diff): Minified ES module build artifact; same pattern as sibling files. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-CJg4-W7Z.cjs | AI (source-diff): Minified Svelte runtime + component code; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2Nd-BsExTc8A.cjs | AI (source-diff): Minified build artifact; includes Microsoft TypeScript helpers copyright notice, clearly legitimate. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-C3O2Twu7.cjs | AI (source-diff): Minified build artifact; content is standard component code with limit-type config objects. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2Nd-tteQ2Pcq.cjs | AI (source-diff): Minified Svelte/Stencil build artifact; readable i18n strings and standard helpers confirm legitimate compiled output. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-X90r5Ee7.cjs | AI (source-diff): Standard minified Svelte/Stencil bundle output. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal iGaming component package; no repo/deps expected for private JFrog-published widget library. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-CzSefvqX.js | AI (source-diff): Standard minified Svelte/Stencil bundle output. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-CNVxhaGt.js | AI (source-diff): Standard minified Svelte/Stencil bundle output. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-IkOsUuVt.js | AI (source-diff): Standard minified Svelte/Stencil bundle output. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2Nd-i9DoJ_7Y.cjs | AI (source-diff): Standard minified Svelte/Stencil bundle output; consistent across all 199 versions of this package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16Nd-DbUDIYJ2.js | AI (source-diff): Standard minified Svelte/Stencil bundle output. | ai | |
| source-diff | obfuscated-file:components/PlayerLimitNotification-DdtD4G0H.cjs | AI (source-diff): Standard minified Svelte/Stencil bundle output. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2Nd-4rpnhWgV.cjs | AI (source-diff): Standard minified Svelte/Stencil bundle output. | ai |
Versions (showing 51 of 117)
| Version | Deps | Published |
|---|---|---|
| 0.14.20 | 0 / 0 | |
| 0.14.19 | 0 / 0 | |
| 0.14.18 | 0 / 0 | |
| 0.14.17 | 0 / 0 | |
| 0.14.16 | 0 / 0 | |
| 0.14.15 | 0 / 0 | |
| 0.14.9 | 0 / 0 | |
| 0.14.8 | 0 / 0 | |
| 0.14.7 | 0 / 0 | |
| 0.14.6 | 0 / 0 | |
| 0.14.5 | 0 / 0 | |
| 0.14.4 | 0 / 0 | |
| 0.14.3 | 0 / 0 | |
| 0.14.2 | 0 / 0 | |
| 0.14.1 | 0 / 0 | |
| 0.14.0 | 0 / 0 | |
| 0.13.15 | 0 / 0 | |
| 0.13.14 | 0 / 0 | |
| 0.13.13 | 0 / 0 | |
| 0.13.12 | 0 / 0 | |
| 0.13.11 | 0 / 0 | |
| 0.13.10 | 0 / 0 | |
| 0.13.9 | 0 / 0 | |
| 0.13.8 | 0 / 0 | |
| 0.13.7 | 0 / 0 | |
| 0.13.6 | 0 / 0 | |
| 0.13.5 | 0 / 0 | |
| 0.13.4 | 0 / 0 | |
| 0.13.3 | 0 / 0 | |
| 0.13.2 | 0 / 0 | |
| 0.13.1 | 0 / 0 | |
| 0.13.0 | 0 / 0 | |
| 0.12.8 | 0 / 0 | |
| 0.12.7 | 0 / 0 | |
| 0.12.6 | 0 / 0 | |
| 0.12.5 | 0 / 0 | |
| 0.12.4 | 0 / 0 | |
| 0.12.3 | 0 / 0 | |
| 0.12.2 | 0 / 0 | |
| 0.12.1 | 0 / 0 | |
| 0.12.0 | 0 / 0 | |
| 0.11.2 | 0 / 0 | |
| 0.11.1 | 0 / 0 | |
| 0.11.0 | 0 / 0 | |
| 0.10.37 | 0 / 0 | |
| 0.10.36 | 0 / 0 | |
| 0.10.35 | 0 / 0 | |
| 0.10.34 | 0 / 0 | |
| 0.10.33 | 0 / 0 | |
| 0.10.32 | 0 / 0 | |
| 0.10.31 | 0 / 0 |
v0.14.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (goe.suta) than the most recent previously approved version (adrian.pripon) on 2026-05-26, but goe.suta is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.14.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.
v0.14.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.
v0.14.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.
v0.14.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.
v0.14.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.
v0.14.4
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.
v0.14.3
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.
v0.14.2
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.
v0.14.1
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.
v0.14.0
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.
v0.13.15
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.
v0.13.14
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.
v0.13.13
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.
v0.13.12
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.
v0.13.11
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.
v0.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
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.
v0.12.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.
v0.12.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.
v0.12.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.
v0.12.1
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.
v0.10.36
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.
v0.10.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.