@everymatrix/player-account-gaming-limits-wrapper-2
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/PlayerAccountGamingLimitsHistory2-CZGhwjrX.cjs | AI (source-diff): Standard Rollup/Vite minified build output for this Stencil/Svelte component package; stable pattern across versions. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-H4qomKzR.cjs | AI (source-diff): Standard Rollup/Vite minified build output; Svelte runtime helpers visible in sample. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-DZMqJQfh.cjs | AI (source-diff): Standard Rollup/Vite minified build output; readable i18n and limit-type config visible in sample. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-ChVLo9iM.js | AI (source-diff): Minified build artifact from Svelte/Stencil component build; consistent with package's established pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-BAuFPQ6k.js | AI (source-diff): Minified build artifact from Svelte/Stencil component build; consistent with package's established pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-EdwtIqld.js | AI (source-diff): Minified build artifact from Svelte/Stencil component build; consistent with package's established pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-wW8APCpG.js | AI (source-diff): Minified build artifact from Svelte/Stencil component build; consistent with package's established pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2--pMxi7h_.js | AI (source-diff): Svelte runtime + component bundle; standard minified build output. | ai | |
| source-diff | obfuscated-file:stencil/ui-skeleton-ed169f8f-cGTgZqRU.cjs | AI (source-diff): Stencil skeleton loader component; standard minified build output. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-DfdGTG35.cjs | AI (source-diff): Minified component bundle with gaming limits UI strings; consistent with package purpose. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-LFOZXQpH.js | AI (source-diff): Minified component bundle; standard build output consistent with package purpose. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-INO_H_dt.js | AI (source-diff): Minified component bundle; standard build output consistent with package purpose. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2-CT79tQyK.js | AI (source-diff): Svelte runtime + component bundle; standard minified build output. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-TJn8VP72.cjs | AI (source-diff): Minified component bundle with gaming limits UI strings; consistent with package purpose. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2-hvfzw72t.cjs | AI (source-diff): Svelte/Stencil minified component bundle; no malicious indicators, matches package purpose. | ai | |
| source-diff | obfuscated-file:stencil/index-b2193545-CQaBo5im.cjs | AI (source-diff): Standard Stencil.js minified build output; consistent with this package's component library pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-9Zpm2qBo.cjs | AI (source-diff): Standard Rollup/Vite minified build output for a UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-DpVjfsIL.js | AI (source-diff): Standard Rollup/Vite minified build output for a UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-D4uSSrhJ.js | AI (source-diff): Standard Rollup/Vite minified build output for a UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-DAf67z-e.js | AI (source-diff): Standard Rollup/Vite minified build output for a UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-DAoJ9OdT.cjs | AI (source-diff): Standard Rollup/Vite minified build output for a UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-C241XmYb.js | AI (source-diff): Standard Rollup/Vite minified build output for a UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2-DJTRTnq0.cjs | AI (source-diff): Standard Rollup/Vite minified build output for a UI component; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-K3a3Z1aO.js | AI (source-diff): Standard Svelte/Stencil build output; consistent with prior versions of this corporate component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2-ANPXP-52.cjs | AI (source-diff): Standard Svelte/Stencil build output; consistent with prior versions of this corporate component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-DZ09c_9w.cjs | AI (source-diff): Standard Svelte/Stencil build output; consistent with prior versions of this corporate component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-QJTkLiWf.cjs | AI (source-diff): Standard Svelte/Stencil build output; consistent with prior versions of this corporate component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-De28BsRr.js | AI (source-diff): Standard Svelte/Stencil build output; consistent with prior versions of this corporate component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-C3M89rk3.js | AI (source-diff): Standard Svelte/Stencil build output; consistent with prior versions of this corporate component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-DhvqBlIs.js | AI (source-diff): Standard Svelte/Stencil build output; consistent with prior versions of this corporate component package. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-Btif_Qyp.js | AI (source-diff): Standard Vite/Rollup minified build output; readable domain logic visible in samples, no malicious indicators. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-h7Us3C6g.js | AI (source-diff): Standard Vite/Rollup minified build output; readable domain logic visible in samples, no malicious indicators. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-CWEBMz7Q.js | AI (source-diff): Standard Vite/Rollup minified build output; readable domain logic visible in samples, no malicious indicators. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-BV5xiyWZ.js | AI (source-diff): Standard Vite/Rollup minified build output; readable domain logic visible in samples, no malicious indicators. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @everymatrix component packages; not a malware indicator here. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-DlAFc5z6.cjs | AI (source-diff): Standard minified Svelte/Stencil build output; consistent with this package's established pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal component library; no repo/keywords/deps is normal for this package family. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2-Bc2GocKF.cjs | AI (source-diff): Standard minified Svelte/Stencil build output; consistent with this package's established pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-B2Jpkb3R.cjs | AI (source-diff): Standard minified Svelte/Stencil build output; consistent with this package's established pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-CxQb7Dib.js | AI (source-diff): Standard minified Svelte/Stencil build output; consistent with this package's established pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-baWt3MEz.js | AI (source-diff): Standard minified Svelte/Stencil build output; consistent with this package's established pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2-xW745gmo.js | AI (source-diff): Standard minified Svelte/Stencil build output; consistent with this package's established pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2-Jx1aCqla.js | AI (source-diff): Standard minified Svelte/Stencil build output; consistent with this package's established pattern. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-DLzmJXwu.cjs | AI (source-diff): Standard Rollup/Vite minified build output; Svelte runtime + component logic only. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-WGfOvs6R.js | AI (source-diff): Standard Rollup/Vite minified ESM build output; Svelte runtime helpers only. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsWrapper2-BN9qszwB.js | AI (source-diff): Standard Rollup/Vite minified ESM build output; Svelte runtime + component logic only. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-BUDAhgXC.js | AI (source-diff): Standard Rollup/Vite minified ESM build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-B3ME-bHd.js | AI (source-diff): Standard Rollup/Vite minified ESM build output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsPage2Gm16-PGOG8UtP.cjs | AI (source-diff): Standard Rollup/Vite minified build output; contains only UI/i18n logic. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountGamingLimitsHistory2-BQ_O7Xp9.cjs | AI (source-diff): Standard Rollup/Vite minified build output for a Svelte UI component; no malicious patterns. | ai | |
| provenance | publisher-changed | AI (provenance): adrian.pripon is an established @everymatrix org publisher with 1789 approvals; transition appears legitimate. | ai |
Versions (showing 51 of 287)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 1.92.1 | 0 / 0 |
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
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.27
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.26
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.25
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.24
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.23
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.22
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.21
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.19
6 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.
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
6 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.
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
6 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.
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
6 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.
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
6 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.
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
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.8
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.7
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.6
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.5
5 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.
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
1 findingPackage 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
1 findingPackage 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.12
1 findingPackage 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.
v1.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.