← Home

@everymatrix/casino-tournaments-thumbnail

npm
29
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/CasinoTournamentsThumbnail-s_EUdQAX.js AI (source-diff): Standard minified Svelte/Stencil component build output; stable for this package. ai
source-diff obfuscated-file:components/CasinoTournamentsThumbnail-Dh8gm7H6.cjs AI (source-diff): Standard minified Svelte/Stencil component build output; stable for this package. ai
source-diff obfuscated-file:components/CasinoTournamentsThumbnail-BD1PnxJ-.js AI (source-diff): Standard minified Svelte/Stencil component build output; stable for this package. ai
source-diff obfuscated-file:components/CasinoTournamentsThumbnail-C-1gtb8z.js AI (source-diff): Standard minified Svelte/Stencil build output; consistent with package's established build artifact pattern. ai
source-diff obfuscated-file:components/CasinoTournamentsThumbnail-BlEoEBx3.cjs AI (source-diff): Standard minified Svelte/Stencil build output; consistent with package's established build artifact pattern. ai
source-diff obfuscated-file:components/CasinoTournamentsThumbnail-DLVdcaz-.js AI (source-diff): Standard minified Svelte/Stencil build output; consistent with package's established build artifact pattern. ai
bogus-package bogus-package AI (bogus-package): Internal component library in a large monorepo; no deps/repo/keywords is consistent across all 1027 versions. ai
provenance no-provenance AI (provenance): No provenance has been present across all versions; stable false positive for this package. ai
npm-metadata no-description AI (npm-metadata): Stable pattern for this internal component package across all versions. ai

Versions (showing 29 of 230)

Version Deps Published
1.74.8 0 / 0
1.74.7 0 / 0
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.8

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.