← Home

@everymatrix/player-gaming-history

npm
51
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:components/PlayerAccountGamingLimitsInfoCard-D_Gu4ZW5.js AI (source-diff): Minified Svelte component bundle; consistent with package pattern. ai
source-diff obfuscated-file:components/PlayerAccountGamingLimitsGroupEdit-y8_MhEQL.js AI (source-diff): Minified Svelte component bundle; consistent with package pattern. ai
source-diff obfuscated-file:components/PlayerAccountGamingLimitsInfoCard-CEK2gvoQ.js AI (source-diff): Minified Svelte component bundle; consistent with package pattern. ai
source-diff obfuscated-file:components/PlayerGamingHistory-WZwkrHpz.cjs AI (source-diff): Standard Vite/Svelte minified bundle output; not obfuscation. ai
source-diff net-exec-file:components/PlayerGamingHistory-WZwkrHpz.cjs AI (source-diff): Svelte runtime fetch+requestAnimationFrame pattern; not dropper malware. ai
source-diff obfuscated-file:components/PlayerGamingHistory-DJ6Y4p90.js AI (source-diff): Standard Vite/Svelte minified bundle output. ai
source-diff net-exec-file:components/PlayerGamingHistory-DJ6Y4p90.js AI (source-diff): Svelte runtime pattern; not dropper malware. ai
source-diff obfuscated-file:components/PlayerGamingHistory-Jfofjvcb.js AI (source-diff): Standard Vite/Svelte minified bundle output. ai
source-diff net-exec-file:components/PlayerGamingHistory-Jfofjvcb.js AI (source-diff): Svelte runtime pattern; not dropper malware. ai
source-diff obfuscated-file:components/PlayerAccountGamingLimitsConfirmationModal-BK9EH9Rt.cjs AI (source-diff): Minified Svelte component bundle; i18n strings and CSS visible in sample. ai
source-diff obfuscated-file:components/PlayerAccountGamingLimitsGroupEdit-CgYe74GU.cjs AI (source-diff): Minified Svelte component bundle; i18n strings visible in sample. ai
source-diff obfuscated-file:components/PlayerAccountGamingLimitsInfoCard-2huuyjT6.cjs AI (source-diff): Minified Svelte component bundle; i18n strings visible in sample. ai
source-diff obfuscated-file:components/PlayerAccountGamingLimitsPopup-BfXocrId.cjs AI (source-diff): Minified Svelte component bundle; i18n strings visible in sample. ai
source-diff obfuscated-file:components/PlayerAccountModal-OXK4ExMf.cjs AI (source-diff): Minified Svelte component bundle; modal logic visible in sample. ai
source-diff obfuscated-file:components/PlayerAccountGamingLimitsGroupEdit-DKVKH_8F.js AI (source-diff): Minified Svelte component bundle; i18n strings visible in sample. ai
bogus-package bogus-package AI (bogus-package): Scoped component library with 837 versions; missing metadata is a known pattern for this publisher, not a spam indicator. ai
semgrep semgrep:new-function-constructor AI (semgrep): Fires inside Vaadin dev-mode detection boilerplate; stable false positive for this component package. ai

Versions (showing 51 of 188)

View all versions
Version Deps Published
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.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
1.92.0 0 / 0
1.91.2 0 / 0
1.91.1 0 / 0
1.90.37 0 / 0
1.90.36 0 / 0
1.90.35 0 / 0
1.90.34 0 / 0
1.90.33 0 / 0
1.90.32 0 / 0
1.90.31 0 / 0
1.90.30 0 / 0
1.90.29 0 / 0

v1.94.30

1 finding
LOW No provenance attestation provenance

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

v1.94.29

1 finding
LOW No provenance attestation provenance

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

v1.94.28

1 finding
LOW No provenance attestation provenance

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

v1.94.27

1 finding
LOW No provenance attestation provenance

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

v1.94.26

1 finding
LOW No provenance attestation provenance

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

v1.94.25

1 finding
LOW No provenance attestation provenance

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

v1.94.24

1 finding
LOW No provenance attestation provenance

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

v1.94.23

1 finding
LOW No provenance attestation provenance

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

v1.94.22

1 finding
LOW No provenance attestation provenance

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

v1.94.21

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-06-01, 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-06-01, 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.4

16 findings
HIGH New obfuscated file: components/PlayerAccountGamingLimitsConfirmationModal-BK9EH9Rt.cjs source-diff

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

HIGH New obfuscated file: components/PlayerAccountGamingLimitsGroupEdit-CgYe74GU.cjs source-diff

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

HIGH New obfuscated file: components/PlayerAccountGamingLimitsInfoCard-2huuyjT6.cjs source-diff

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

HIGH New obfuscated file: components/PlayerAccountGamingLimitsPopup-BfXocrId.cjs source-diff

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

HIGH New obfuscated file: components/PlayerAccountModal-OXK4ExMf.cjs source-diff

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

HIGH New obfuscated file: components/PlayerGamingHistory-WZwkrHpz.cjs source-diff

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

HIGH New file with network + code execution: components/PlayerGamingHistory-WZwkrHpz.cjs source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: components/PlayerAccountGamingLimitsGroupEdit-DKVKH_8F.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.

HIGH New obfuscated file: components/PlayerAccountGamingLimitsGroupEdit-y8_MhEQL.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.

HIGH New obfuscated file: components/PlayerAccountGamingLimitsInfoCard-CEK2gvoQ.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.

HIGH New obfuscated file: components/PlayerAccountGamingLimitsInfoCard-D_Gu4ZW5.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.

HIGH New obfuscated file: components/PlayerGamingHistory-DJ6Y4p90.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.

HIGH New file with network + code execution: components/PlayerGamingHistory-DJ6Y4p90.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: components/PlayerGamingHistory-Jfofjvcb.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.

HIGH New file with network + code execution: components/PlayerGamingHistory-Jfofjvcb.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v1.94.3

1 finding
LOW No provenance attestation provenance

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

v1.94.2

1 finding
LOW No provenance attestation provenance

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

v1.94.1

1 finding
LOW No provenance attestation provenance

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

v1.94.0

1 finding
LOW No provenance attestation provenance

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

v1.93.15

1 finding
LOW No provenance attestation provenance

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

v1.93.14

1 finding
LOW No provenance attestation provenance

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

v1.93.13

1 finding
LOW No provenance attestation provenance

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

v1.93.12

1 finding
LOW No provenance attestation provenance

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

v1.93.11

1 finding
LOW No provenance attestation provenance

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

v1.93.10

1 finding
LOW No provenance attestation provenance

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

v1.93.9

1 finding
LOW No provenance attestation provenance

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

v1.93.8

1 finding
LOW No provenance attestation provenance

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

v1.93.7

1 finding
LOW No provenance attestation provenance

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

v1.93.6

1 finding
LOW No provenance attestation provenance

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

v1.93.5

1 finding
LOW No provenance attestation provenance

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

v1.93.2

1 finding
LOW No provenance attestation provenance

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

v1.93.1

1 finding
LOW No provenance attestation provenance

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

v1.93.0

1 finding
LOW No provenance attestation provenance

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

v1.92.7

1 finding
LOW No provenance attestation provenance

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

v1.92.6

1 finding
LOW No provenance attestation provenance

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

v1.92.5

1 finding
LOW No provenance attestation provenance

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

v1.92.4

1 finding
LOW No provenance attestation provenance

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

v1.92.3

1 finding
LOW No provenance attestation provenance

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

v1.92.2

1 finding
LOW No provenance attestation provenance

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

v1.92.1

1 finding
LOW No provenance attestation provenance

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

v1.92.0

1 finding
LOW No provenance attestation provenance

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

v1.91.2

1 finding
LOW No provenance attestation provenance

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

v1.91.1

1 finding
LOW No provenance attestation provenance

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

v1.90.37

1 finding
LOW No provenance attestation provenance

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

v1.90.36

1 finding
LOW No provenance attestation provenance

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

v1.90.35

1 finding
LOW No provenance attestation provenance

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

v1.90.34

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.

v1.90.33

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.

v1.90.32

1 finding
LOW No provenance attestation provenance

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

v1.90.31

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.

v1.90.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.

v1.90.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.