← Home

@everymatrix/casino-challenges-claim-code

npm
100
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

clokzeoleksandr.v.stepanovtaras.maksymivnatalya.anisimovaemfe_releasemariana.gheorgheadrian.priponandriizadvirnyiraulvasileemstrulea.sebastianstefan.vladgoe.sutadragos.bodeamaria.bumbarstefanaotong.woodtikarncatalinpoclidliviuclement.everymatrixmihaibalanfrankie24

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js AI (source-diff): Standard Stencil minified build output for this widget package; not malicious obfuscation. ai
source-diff obfuscated-file:dist/casino-challenges-claim-code/casino-challenges-claim-code-3171841e.js AI (source-diff): Standard minified Stencil component build output; stable pattern for this widget package. ai
source-diff obfuscated-file:dist/casino-challenges-claim-code/casino-challenges-claim-code-d1142ba4.js AI (source-diff): Standard minified Stencil web-component bundle; sample shows benign widget logic, no obfuscation indicators. ai
source-diff obfuscated-file:dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js AI (source-diff): Standard minified Stencil web-component bundle; sample confirms legitimate widget logic, not obfuscated malware. ai
source-diff obfuscated-file:dist/casino-challenges-claim-code/casino-challenges-claim-code-f585a2d9.js AI (source-diff): Standard minified Stencil web-component bundle; content is readable casino widget logic, not obfuscated malware. ai
provenance publisher-changed AI (provenance): emfe_release is the established org release account for @everymatrix scope with 11k+ approved packages; transition from individual to org account is expected. ai
source-diff obfuscated-file:dist/casino-challenges-claim-code/casino-challenges-claim-code-688742ee.js AI (source-diff): Standard Stencil/Vite minified build output; content is readable and benign across versions of this package. ai
source-diff obfuscated-file:dist/casino-challenges-claim-code/casino-challenges-claim-code-3f09ef18.js AI (source-diff): Standard Stencil/Rollup minified bundle output; content is readable widget logic, not obfuscation. ai
bogus-package bogus-package AI (bogus-package): Scoped monorepo UI component; empty deps and minimal metadata are expected for this package family. ai
npm-metadata no-description AI (npm-metadata): Consistent across all 226 versions of this everymatrix component library package. ai

Versions (showing 100 of 162)

Version Deps Published
0.17.29 0 / 0
0.17.28 0 / 0
0.17.27 0 / 0
0.17.26 0 / 0
0.17.25 0 / 0
0.17.24 0 / 0
0.17.23 0 / 0
0.17.22 0 / 0
0.17.21 0 / 0
0.17.20 0 / 0
0.17.19 0 / 0
0.17.18 0 / 0
0.17.17 0 / 0
0.17.16 0 / 0
0.17.15 0 / 0
0.17.9 0 / 0
0.17.8 0 / 0
0.17.7 0 / 0
0.17.6 0 / 0
0.17.5 0 / 0
0.17.4 0 / 0
0.17.3 0 / 0
0.17.2 0 / 0
0.17.1 0 / 0
0.17.0 0 / 0
0.16.15 0 / 0
0.16.14 0 / 0
0.16.13 0 / 0
0.16.12 0 / 0
0.16.11 0 / 0
0.16.10 0 / 0
0.16.9 0 / 0
0.16.8 0 / 0
0.16.7 0 / 0
0.16.6 0 / 0
0.16.5 0 / 0
0.16.4 0 / 0
0.16.3 0 / 0
0.16.2 0 / 0
0.16.1 0 / 0
0.16.0 0 / 0
0.15.8 0 / 0
0.15.7 0 / 0
0.15.6 0 / 0
0.15.5 0 / 0
0.15.4 0 / 0
0.15.3 0 / 0
0.15.2 0 / 0
0.15.1 0 / 0
0.15.0 0 / 0
0.14.2 0 / 0
0.14.1 0 / 0
0.14.0 0 / 0
0.13.37 0 / 0
0.13.36 0 / 0
0.13.35 0 / 0
0.13.34 0 / 0
0.13.33 0 / 0
0.13.32 0 / 0
0.13.31 0 / 0
0.13.30 0 / 0
0.13.29 0 / 0
0.13.28 0 / 0
0.13.27 0 / 0
0.13.26 0 / 0
0.13.25 0 / 0
0.13.24 0 / 0
0.13.9 0 / 0
0.13.6 0 / 0
0.13.3 0 / 0
0.13.2 0 / 0
0.12.1 0 / 0
0.12.0 0 / 0
0.11.23 0 / 0
0.11.19 0 / 0
0.11.16 0 / 0
0.11.13 0 / 0
0.11.12 0 / 0
0.11.11 0 / 0
0.11.10 0 / 0
0.10.44 0 / 0
0.10.42 0 / 0
0.10.40 0 / 0
0.10.37 0 / 0
0.10.28 0 / 0
0.10.6 0 / 0
0.9.29 0 / 0
0.9.12 0 / 0
0.9.11 0 / 0
0.9.10 0 / 0
0.9.9 0 / 0
0.9.8 0 / 0
0.9.7 0 / 0
0.9.6 0 / 0
0.9.5 0 / 0
0.9.4 0 / 0
0.9.3 0 / 0
0.9.2 0 / 0
0.9.1 0 / 0
0.9.0 0 / 0
Showing 100 of 162 Next page →

v0.17.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.15

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: adrian.pripon → goe.suta (on 2026-05-26, known maintainer) provenance

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.17.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.2

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-3f09ef18.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.1

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-3f09ef18.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-3f09ef18.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.8

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-3f09ef18.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.7

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-3f09ef18.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.6

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-3f09ef18.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.37

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.36

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.34

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.33

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.28

3 findings
HIGH Publisher changed: emfe_release → adrian.pripon (on 2026-03-26) provenance

This version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.27

3 findings
HIGH Publisher changed: emfe_release → adrian.pripon (on 2026-03-25) provenance

This version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.26

3 findings
HIGH Publisher changed: emfe_release → adrian.pripon (on 2026-03-24) provenance

This version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.25

3 findings
HIGH Publisher changed: emfe_release → adrian.pripon (on 2026-03-24) provenance

This version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.24

3 findings
HIGH Publisher changed: emfe_release → adrian.pripon (on 2026-03-23) provenance

This version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.9

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-03-10) provenance

This version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.6

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-03-06) provenance

This version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.3

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-03-04) provenance

This version was published by a different npm account than previous versions on 2026-03-04. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.2

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-03-04) provenance

This version was published by a different npm account than previous versions on 2026-03-04. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.1

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-02-27) provenance

This version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-02-26) provenance

This version was published by a different npm account than previous versions on 2026-02-26. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.23

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-02-25) provenance

This version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.19

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-02-23) provenance

This version was published by a different npm account than previous versions on 2026-02-23. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.16

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-02-19) provenance

This version was published by a different npm account than previous versions on 2026-02-19. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-98d119cc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.40

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-01-30) provenance

This version was published by a different npm account than previous versions on 2026-01-30. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-f585a2d9.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.37

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-01-29) provenance

This version was published by a different npm account than previous versions on 2026-01-29. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-f585a2d9.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.28

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-01-21) provenance

This version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-3171841e.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.6

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2026-01-02) provenance

This version was published by a different npm account than previous versions on 2026-01-02. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.29

3 findings
HIGH Publisher changed: emfe_release → strulea.sebastian (on 2025-12-25) provenance

This version was published by a different npm account than previous versions on 2025-12-25. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.12

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.11

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.10

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.9

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.8

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.7

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.6

3 findings
HIGH Publisher changed: emfe_release → adrian.pripon (on 2025-12-03) provenance

This version was published by a different npm account than previous versions on 2025-12-03. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.5

2 findings
HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.4

3 findings
HIGH Publisher changed: emfe_release → maria.bumbar (on 2025-12-02) provenance

This version was published by a different npm account than previous versions on 2025-12-02. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.3

3 findings
HIGH Publisher changed: emfe_release → maria.bumbar (on 2025-12-02) provenance

This version was published by a different npm account than previous versions on 2025-12-02. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/casino-challenges-claim-code/casino-challenges-claim-code-b1eeb8bc.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.