@everymatrix/casino-header-controller-nd
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-BWo6pPAT.cjs | AI (source-diff): Minified Stencil/Svelte bundle output, not true obfuscation; no malicious behavior. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-B_hZ2HH0.cjs | AI (source-diff): Bundled Svelte/Stencil output, not true obfuscation; consistent with prior versions. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-DEwyy8XP.cjs | AI (source-diff): Minified bundler output for frontend component, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@everymatrix/casino-hamburger-menu-nd | AI (phantom-deps): Same-org dependency; likely transitive or re-exported in monorepo. | ai | |
| phantom-deps | phantom-dep:@everymatrix/player-account-balance-modal-nd | AI (phantom-deps): Same-org dependency; likely transitive or re-exported in monorepo. | ai | |
| phantom-deps | phantom-dep:@everymatrix/player-deposit | AI (phantom-deps): Same-org dependency; likely transitive or re-exported in monorepo. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-Dy_ZPbVP.cjs | AI (source-diff): Bundled Stencil/Rollup component output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-NxKPo2-K.cjs | AI (source-diff): Bundled Stencil/esbuild component output, not true obfuscation. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): Build tool used in npm scripts; not a runtime dependency. | ai | |
| phantom-deps | phantom-dep:sirv-cli | AI (phantom-deps): Dev server; referenced in start script, not runtime code. | ai | |
| phantom-deps | phantom-dep:svelte | AI (phantom-deps): Svelte framework; referenced in build config and scripts, not direct imports. | ai | |
| source-diff | obfuscated-file:lazy/user-deposit-withdrawal-Bc0EXV1Q.cjs | AI (source-diff): Minified bundler output, matches package's stated widget components. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-CoGcq6kJ.js | AI (source-diff): Minified bundler output, matches package's stated widget components. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-DDXOWtfA.cjs | AI (source-diff): Minified bundler output, matches package's stated widget components. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-Doj1YIkv.cjs | AI (source-diff): Minified bundler output, matches package's stated widget components. | ai | |
| source-diff | obfuscated-file:stencil/player-step-up-auth_2-COWt1iEx.cjs | AI (source-diff): Minified bundler output, matches package's stated widget components. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-dDVOJgyI.cjs | AI (source-diff): Minified bundler output for legit component, not true obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher has long approved track record; no evidence of takeover. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-DonDLA4M.js | AI (source-diff): Minified bundler output, matches package's stated widget components. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-D-QbQo5l.js | AI (source-diff): Bundled build output, standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-BJfmzqdu.js | AI (source-diff): Bundled build output, standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-BQYwD0K7.js | AI (source-diff): Bundled build output, standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-CCqdYPC9.cjs | AI (source-diff): Bundled build output, standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-CoRWx72W.cjs | AI (source-diff): Bundled build output, standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-CCYauW0e.cjs | AI (source-diff): Bundled Stencil/Svelte build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-DpoEVTD2.cjs | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-DU25a-Pj.js | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-DG8tZ1HV.js | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerDeposit-CxN8IRSF.cjs | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-Dh9fsAYn.js | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-BrVqd8fj.js | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:lazy/user-deposit-withdrawal-j3vQXCPl.cjs | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-DC0YUiyt.js | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-D37mIOCZ.js | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-BubwOF4n.cjs | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-DDz9SBMv.cjs | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:stencil/player-step-up-auth_2-B-1QyGOd.cjs | AI (source-diff): Bundled minified build output, not obfuscation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Known org publishing pattern with rotating maintainers, no takeover evidence. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal component lib naming convention; stable false positive. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-BWhQR6n1.cjs | AI (source-diff): Minified bundle output, not true obfuscation; no malicious behavior present. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Expected growth from bundler output across many components. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Long-standing internal EveryMatrix component lib, sparse metadata is normal for this org's publishing style. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-DVSBR7nU.cjs | AI (source-diff): Bundled Stencil/Vite build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-BrHzveo7.cjs | AI (source-diff): Bundled Stencil/Vite build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:stencil/gamification-dropdown-DjgYvWgI.js | AI (source-diff): Standard minified Stencil build output. | ai | |
| source-diff | obfuscated-file:stencil/gamification-dropdown-Aq4yHgGB.js | AI (source-diff): Standard minified Stencil build output. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-4P6rbd_i.js | AI (source-diff): Standard minified Svelte/Stencil build output. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-1s11bD3E.js | AI (source-diff): Standard minified Svelte/Stencil build output. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-Ct2xeBTP.js | AI (source-diff): Standard minified Svelte/Stencil build output. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-BZ-tSGqC.js | AI (source-diff): Standard minified Svelte/Stencil build output. | ai | |
| source-diff | obfuscated-file:components/PlayerDeposit-CHdUIP9F.cjs | AI (source-diff): Standard minified Svelte/Stencil build output. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-Dy0J1BNv.cjs | AI (source-diff): Standard minified Svelte/Stencil build output. | ai | |
| source-diff | obfuscated-file:stencil/player-rakeback-card-BG3ZIhV3.cjs | AI (source-diff): Standard minified Stencil build output. | ai | |
| source-diff | obfuscated-file:stencil/player-elevate-pointcard-DdkpqBvL.cjs | AI (source-diff): Standard minified Stencil build output. | ai | |
| source-diff | obfuscated-file:stencil/player-elevate-card-items-a0f9711e-BcCKrobp.cjs | AI (source-diff): Standard minified Stencil build output with date-fns code. | ai | |
| source-diff | obfuscated-file:stencil/player-elevate-card-D4DBOUoV.cjs | AI (source-diff): Standard minified Stencil build output. | ai | |
| source-diff | obfuscated-file:stencil/gamification-dropdown-f420baf5-CXS6ttXg.cjs | AI (source-diff): Standard minified Stencil build output. | ai | |
| source-diff | obfuscated-file:stencil/gamification-dropdown-C0KSnS-f.cjs | AI (source-diff): Standard minified Stencil build output. | ai | |
| source-diff | obfuscated-file:lazy/gamification-dropdown-1FoOgZ8Q.cjs | AI (source-diff): Standard minified Stencil lazy-load bundle. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-DxVp8qmB.cjs | AI (source-diff): Standard minified Svelte/Stencil build output; no malicious patterns in samples. | ai | |
| source-diff | obfuscated-file:stencil/gamification-dropdown_4-DYrDHhuq.cjs | AI (source-diff): Standard minified Stencil build output. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-DSiWs0I6.js | AI (source-diff): Standard minified Svelte/Stencil build output. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-CwwjFYp7.js | AI (source-diff): Standard minified Svelte/Stencil build output. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-k9DtpKud.cjs | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-CwqPWK1V.js | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-CpaGBDBv.js | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:stencil/gamification-dropdown-oHavdEUT.js | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:stencil/gamification-dropdown-DFnrjTD-.js | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-S7CB2Zm1.js | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-CvuXdH5B.js | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-C1BwrBUZ.js | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd--iNvdWKM.js | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerDeposit-NUlqpRDD.cjs | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-CFwzUwp9.cjs | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHamburgerMenuNd-CgUiUufD.cjs | AI (source-diff): Standard Svelte/Vite minified build output; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-_NylOeXH.cjs | AI (source-diff): Standard Rollup/Vite minified build output for this package family; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-BrvRNp2P.js | AI (source-diff): Standard Rollup/Vite minified build output for this package family; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/PlayerAccountBalanceModalNd-BoSGIXIA.js | AI (source-diff): Standard Rollup/Vite minified build output for this package family; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-nGf5Fo6G.js | AI (source-diff): Standard Rollup/Vite minified build output for this package family; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-DIOpuptV.js | AI (source-diff): Standard Rollup/Vite minified build output for this package family; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:components/CasinoHeaderControllerNd-ClL-p2I1.cjs | AI (source-diff): Standard Rollup/Vite minified build output for this package family; not malicious obfuscation. | ai |
Versions (showing 100 of 333)
| Version | Deps | Published |
|---|---|---|
| 1.87.38 | 0 / 0 | |
| 1.87.36 | 0 / 0 | |
| 1.87.35 | 0 / 0 | |
| 1.87.34 | 0 / 0 | |
| 1.87.33 | 0 / 0 | |
| 1.87.26 | 0 / 0 | |
| 1.87.21 | 0 / 0 | |
| 1.87.20 | 0 / 0 | |
| 1.87.18 | 0 / 0 | |
| 1.87.17 | 0 / 0 | |
| 1.87.16 | 0 / 0 | |
| 1.87.15 | 0 / 0 | |
| 1.87.14 | 0 / 0 | |
| 1.87.13 | 0 / 0 | |
| 1.87.5 | 0 / 0 | |
| 1.87.4 | 0 / 0 | |
| 1.86.25 | 0 / 0 | |
| 1.86.11 | 0 / 0 | |
| 1.85.11 | 0 / 0 | |
| 1.85.9 | 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 | |
| 1.77.22 | 0 / 0 | |
| 1.77.21 | 0 / 0 | |
| 1.77.20 | 0 / 0 | |
| 1.77.19 | 0 / 0 | |
| 1.77.18 | 0 / 0 | |
| 1.77.17 | 0 / 0 | |
| 1.77.16 | 0 / 0 | |
| 1.77.15 | 0 / 0 | |
| 1.77.14 | 0 / 0 | |
| 1.77.13 | 0 / 0 | |
| 1.77.12 | 0 / 0 | |
| 1.77.11 | 0 / 0 | |
| 1.77.10 | 0 / 0 | |
| 1.77.9 | 0 / 0 | |
| 1.77.8 | 0 / 0 | |
| 1.77.7 | 0 / 0 | |
| 1.77.6 | 0 / 0 | |
| 1.77.5 | 0 / 0 | |
| 1.77.4 | 0 / 0 | |
| 1.77.3 | 0 / 0 | |
| 1.77.2 | 0 / 0 | |
| 1.77.1 | 0 / 0 | |
| 1.77.0 | 0 / 0 | |
| 1.76.15 | 0 / 0 | |
| 1.76.14 | 0 / 0 | |
| 1.76.13 | 0 / 0 | |
| 1.76.12 | 0 / 0 | |
| 1.76.11 | 0 / 0 | |
| 1.76.10 | 0 / 0 | |
| 1.76.9 | 0 / 0 | |
| 1.76.8 | 0 / 0 | |
| 1.76.7 | 0 / 0 |
v1.87.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.5
25 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong 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 (strulea.sebastian) than the most recent previously approved version (emfe_release) on 2026-01-01, but strulea.sebastian 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.87.4
25 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong 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 (strulea.sebastian) than the most recent previously approved version (emfe_release) on 2025-12-31, but strulea.sebastian 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.86.25
25 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong 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 (strulea.sebastian) than the most recent previously approved version (emfe_release) on 2025-12-17, but strulea.sebastian 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.86.11
24 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong 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.11
11 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.9
11 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.77.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.