← Home

@everymatrix/casino-winners

27
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.woodtikarncatalinpoclidcristi.ungureanuliviuclement.everymatrixmihaibalanfrankie24

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:components/CasinoWinners-D8N45SDu.js AI (source-diff): Standard Vite/Svelte minified build output; consistent with package's established build artifact pattern. ai
source-diff obfuscated-file:components/CasinoWinners-CEUoiYda.js AI (source-diff): Standard Vite/Svelte minified build output; consistent with package's established build artifact pattern. ai
source-diff obfuscated-file:components/CasinoWinners-DWUfvyUt.cjs AI (source-diff): Standard Vite/Svelte minified build output; consistent with package's established build artifact pattern. ai
source-diff obfuscated-file:components/CasinoWinners-DW-_K3N0.cjs AI (source-diff): Standard Vite/Svelte minified build output; no malicious patterns. Stable for this package. ai
source-diff obfuscated-file:components/CasinoWinners-CmGboKPh.js AI (source-diff): Standard Vite/Svelte minified build output; no malicious patterns. Stable for this package. ai
source-diff obfuscated-file:components/CasinoWinners-C95GgV_f.js AI (source-diff): Standard Vite/Svelte minified build output; no malicious patterns. Stable for this package. ai
source-diff obfuscated-file:components/CasinoWinners-bp6470MA.js AI (source-diff): Standard minified Svelte bundle output; consistent with package's established build pattern. ai
source-diff obfuscated-file:components/CasinoWinners-Cbt1OuCR.cjs AI (source-diff): Standard minified Svelte bundle output; consistent with package's established build pattern. ai
source-diff obfuscated-file:components/CasinoWinners-By0aVAWJ.js AI (source-diff): Standard minified Svelte bundle output; consistent with package's established build pattern. ai
source-diff obfuscated-file:components/CasinoWinners-C54DMR7B.cjs AI (source-diff): Standard Vite/Svelte minified build output; stable pattern across all versions of this package. ai
source-diff obfuscated-file:components/CasinoWinners-DB4aGWWU.js AI (source-diff): Standard Vite/Svelte minified build output; stable pattern across all versions of this package. ai
source-diff obfuscated-file:components/CasinoWinners-CKA28oZZ.js AI (source-diff): Standard Vite/Svelte minified build output; stable pattern across all versions of this package. ai
provenance no-provenance AI (provenance): No provenance has been used across this package's 686-version history; stable false positive. ai
npm-metadata no-description AI (npm-metadata): Consistent across all @everymatrix/casino-winners versions; not a malice indicator for this package. ai
bogus-package bogus-package AI (bogus-package): @everymatrix scoped packages consistently lack description/repo/keywords; pattern is stable across 686 versions. ai

Versions (showing 27 of 227)

Version Deps Published
1.74.6 0 / 0
1.74.5 0 / 0
1.74.4 0 / 0
1.74.3 0 / 0
1.74.2 0 / 0
1.74.1 0 / 0
1.74.0 0 / 0
1.73.2 0 / 0
1.73.1 0 / 0
1.73.0 0 / 0
1.72.2 0 / 0
1.72.1 0 / 0
1.72.0 0 / 0
1.71.1 0 / 0
1.71.0 0 / 0
1.70.1 0 / 0
1.70.0 0 / 0
1.69.3 0 / 0
1.69.2 0 / 0
1.69.0 0 / 0
1.68.0 0 / 0
1.67.3 0 / 0
1.67.0 0 / 0
1.66.2 0 / 0
1.66.1 0 / 0
1.66.0 0 / 0
1.65.3 0 / 0

v1.74.6

1 finding
INFO No provenance attestation provenance

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

v1.74.5

1 finding
INFO No provenance attestation provenance

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

v1.74.4

1 finding
INFO No provenance attestation provenance

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

v1.74.3

1 finding
INFO No provenance attestation provenance

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

v1.74.2

1 finding
INFO No provenance attestation provenance

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

v1.74.1

1 finding
INFO No provenance attestation provenance

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

v1.74.0

1 finding
INFO No provenance attestation provenance

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

v1.73.2

1 finding
INFO No provenance attestation provenance

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

v1.73.1

1 finding
INFO No provenance attestation provenance

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

v1.73.0

1 finding
INFO No provenance attestation provenance

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

v1.72.2

1 finding
INFO No provenance attestation provenance

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

v1.72.1

1 finding
INFO No provenance attestation provenance

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

v1.72.0

1 finding
INFO No provenance attestation provenance

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

v1.71.1

1 finding
INFO No provenance attestation provenance

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

v1.71.0

1 finding
INFO No provenance attestation provenance

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

v1.70.1

1 finding
INFO No provenance attestation provenance

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

v1.70.0

1 finding
INFO No provenance attestation provenance

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

v1.69.3

1 finding
INFO No provenance attestation provenance

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

v1.69.2

1 finding
INFO No provenance attestation provenance

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

v1.69.0

1 finding
INFO No provenance attestation provenance

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

v1.68.0

1 finding
INFO No provenance attestation provenance

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

v1.67.3

1 finding
INFO No provenance attestation provenance

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

v1.67.0

1 finding
INFO No provenance attestation provenance

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

v1.66.2

1 finding
INFO No provenance attestation provenance

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

v1.66.1

1 finding
INFO No provenance attestation provenance

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

v1.66.0

1 finding
INFO No provenance attestation provenance

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

v1.65.3

1 finding
INFO No provenance attestation provenance

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