← Home

@everymatrix/casino-last-played-section

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:components/CasinoFilter-ur0N0e_q.js AI (source-diff): Standard bundled ESM output for this UI component package. ai
source-diff obfuscated-file:components/CasinoGamesCategorySection-Y8eLR0W5.cjs AI (source-diff): Standard bundled CJS output for this UI component package. ai
source-diff obfuscated-file:components/CasinoFilter-Bq27fkl0.cjs AI (source-diff): Standard bundled CJS output from Vite/Rollup for this UI component package. ai
source-diff obfuscated-file:components/CasinoSort-OyxicsAe.js AI (source-diff): Standard bundled ESM output for this UI component package. ai
source-diff obfuscated-file:components/CasinoSort-CliCKl9a.js AI (source-diff): Standard bundled ESM output for this UI component package. ai
source-diff obfuscated-file:components/CasinoLastPlayedSection-tw4aeVIv.js AI (source-diff): Standard bundled ESM output for this UI component package. ai
source-diff obfuscated-file:components/CasinoLastPlayedSection-jaTKdLsf.js AI (source-diff): Standard bundled ESM output for this UI component package. ai
source-diff obfuscated-file:components/CasinoGameThumbnail-CWi08UB2.js AI (source-diff): Standard bundled ESM output for this UI component package. ai
source-diff obfuscated-file:components/CasinoGameThumbnail-Ck10-v-p.js AI (source-diff): Standard bundled ESM output for this UI component package. ai
source-diff obfuscated-file:components/CasinoGamesCategorySection-BxPHrlVj.js AI (source-diff): Standard bundled ESM output for this UI component package. ai
source-diff obfuscated-file:components/CasinoGamesCategorySection-BIc39Efl.js AI (source-diff): Standard bundled ESM output for this UI component package. ai
source-diff obfuscated-file:components/CasinoFilter-RGuOjNV-.js AI (source-diff): Standard bundled ESM output for this UI component package. ai
source-diff obfuscated-file:components/CasinoSort-CwwPvIGU.cjs AI (source-diff): Standard bundled CJS output for this UI component package. ai
source-diff obfuscated-file:components/CasinoLastPlayedSection-DrrWbeZS.cjs AI (source-diff): Standard bundled CJS output for this UI component package. ai
source-diff obfuscated-file:components/CasinoGameThumbnail-D8eKiOCc.cjs AI (source-diff): Standard bundled CJS output for this UI component package. ai
source-diff obfuscated-file:components/CasinoFilter-Cgt1ZT20.js AI (source-diff): Standard Vite/Rollup minified build output for a casino UI component; not malicious obfuscation. ai
source-diff obfuscated-file:components/CasinoFilter-CytJ8aaW.js AI (source-diff): Standard Vite/Rollup minified build output for a casino UI component; not malicious obfuscation. ai
source-diff obfuscated-file:components/CasinoGamesCategorySection-Dd0pzz6K.js AI (source-diff): Standard Vite/Rollup minified build output for a casino UI component; not malicious obfuscation. ai
source-diff obfuscated-file:components/CasinoGamesCategorySection-VpOhafSe.js AI (source-diff): Standard Vite/Rollup minified build output for a casino UI component; not malicious obfuscation. ai
source-diff obfuscated-file:components/CasinoGameThumbnail-7NVzz92J.js AI (source-diff): Standard Vite/Rollup minified build output for a casino UI component; not malicious obfuscation. ai
source-diff obfuscated-file:components/CasinoGameThumbnail-C8Z5TeV5.js AI (source-diff): Standard Vite/Rollup minified build output for a casino UI component; not malicious obfuscation. ai
source-diff obfuscated-file:components/CasinoLastPlayedSection-xmpsbUK0.js AI (source-diff): Standard Vite/Rollup minified build output; Svelte runtime patterns visible, not malicious obfuscation. ai
source-diff obfuscated-file:components/CasinoLastPlayedSection-z3nPtqoR.js AI (source-diff): Standard Vite/Rollup minified build output; Svelte runtime patterns visible, not malicious obfuscation. ai
source-diff obfuscated-file:components/CasinoSort-Cdc6kies.js AI (source-diff): Standard Vite/Rollup minified build output for a casino UI component; not malicious obfuscation. ai
source-diff obfuscated-file:components/CasinoSort-sVs2Hooi.js AI (source-diff): Standard Vite/Rollup minified build output for a casino UI component; not malicious obfuscation. ai
source-diff obfuscated-file:components/CasinoSort-BUeuRuQI.js AI (source-diff): Standard minified Vite/Rollup bundle output for this component package; stable pattern across versions. ai
source-diff obfuscated-file:components/CasinoFilter--VfGddYk.js AI (source-diff): Standard minified Vite/Rollup bundle output for this component package; stable pattern across versions. ai
source-diff obfuscated-file:components/CasinoFilter-DM4JPD5K.js AI (source-diff): Standard minified Vite/Rollup bundle output for this component package; stable pattern across versions. ai
source-diff obfuscated-file:components/CasinoGamesCategorySection-DK_R_vh_.js AI (source-diff): Standard minified Vite/Rollup bundle output for this component package; stable pattern across versions. ai
source-diff obfuscated-file:components/CasinoGamesCategorySection-EXvHonTz.js AI (source-diff): Standard minified Vite/Rollup bundle output for this component package; stable pattern across versions. ai
source-diff obfuscated-file:components/CasinoGameThumbnail-BU7vXOK3.js AI (source-diff): Standard minified Vite/Rollup bundle output for this component package; stable pattern across versions. ai
source-diff obfuscated-file:components/CasinoGameThumbnail-Djdcfd97.js AI (source-diff): Standard minified Vite/Rollup bundle output for this component package; stable pattern across versions. ai
source-diff obfuscated-file:components/CasinoLastPlayedSection-BwkOHG_v.js AI (source-diff): Standard minified Vite/Rollup bundle output for this component package; stable pattern across versions. ai
source-diff obfuscated-file:components/CasinoLastPlayedSection-CSRzIV5m.js AI (source-diff): Standard minified Vite/Rollup bundle output for this component package; stable pattern across versions. ai
source-diff obfuscated-file:components/CasinoSort-5BbB-x12.js AI (source-diff): Standard minified Vite/Rollup bundle output for this component package; stable pattern across versions. ai
source-diff obfuscated-file:components/CasinoSort-BllIwG-L.js AI (source-diff): Svelte ESM bundle; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoSort-tQyhZT1U.js AI (source-diff): Svelte ESM bundle; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoGameThumbnail-rFXSnS2v.js AI (source-diff): Svelte ESM bundle; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoGameThumbnail-BRddAcBN.js AI (source-diff): Svelte ESM bundle; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoGamesCategorySection-BHDp-KJ4.js AI (source-diff): Svelte ESM bundle; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoGamesCategorySection-6xzUZp3K.js AI (source-diff): Svelte ESM bundle with i18n; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoFilter-BTVMoy_t.js AI (source-diff): Standard Svelte/Rollup ESM bundle; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoFilter-aZNjaj7s.js AI (source-diff): Standard Svelte/Rollup ESM bundle; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoSort-Bjtm0zBv.cjs AI (source-diff): Svelte sort component bundle with i18n; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoLastPlayedSection-ds7jt5iT.cjs AI (source-diff): Svelte component bundle with UI logic; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoGameThumbnail-D5aY7MyL.cjs AI (source-diff): Minified bundle including moment.js; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoGamesCategorySection-k99QzULe.cjs AI (source-diff): Standard Svelte/Rollup minified bundle with i18n strings; no malicious patterns. ai
source-diff obfuscated-file:components/CasinoFilter-ChNOJ2MK.cjs AI (source-diff): Standard Svelte/Rollup minified bundle; no malicious patterns in samples. ai
npm-metadata no-description AI (npm-metadata): Consistent across all versions of this package; not an indicator of malice here. ai
provenance no-provenance AI (provenance): No provenance has been provided across this package's history; stable false positive. ai
bogus-package bogus-package AI (bogus-package): Established scoped component package from EveryMatrix; sparse metadata is a consistent pattern across 624 versions. ai

Versions (showing 100 of 247)

Version Deps Published
1.85.20 0 / 0
1.85.19 0 / 0
1.85.18 0 / 0
1.85.17 0 / 0
1.85.16 0 / 0
1.85.15 0 / 0
1.85.14 0 / 0
1.85.13 0 / 0
1.85.12 0 / 0
1.85.11 0 / 0
1.85.10 0 / 0
1.85.9 0 / 0
1.85.8 0 / 0
1.85.7 0 / 0
1.85.6 0 / 0
1.85.5 0 / 0
1.85.4 0 / 0
1.85.3 0 / 0
1.85.2 0 / 0
1.85.1 0 / 0
1.85.0 0 / 0
1.84.3 0 / 0
1.84.2 0 / 0
1.84.1 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.14 0 / 0
1.76.13 0 / 0
1.76.12 0 / 0
1.76.11 0 / 0
1.76.10 0 / 0
Showing 100 of 247 Next page →

v1.85.20

14 findings
HIGH New obfuscated file: components/CasinoFilter-ChNOJ2MK.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/CasinoGamesCategorySection-k99QzULe.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/CasinoGameThumbnail-D5aY7MyL.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/CasinoLastPlayedSection-ds7jt5iT.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/CasinoSort-Bjtm0zBv.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/CasinoFilter-aZNjaj7s.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/CasinoFilter-BTVMoy_t.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/CasinoGamesCategorySection-6xzUZp3K.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/CasinoGamesCategorySection-BHDp-KJ4.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/CasinoGameThumbnail-BRddAcBN.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/CasinoGameThumbnail-rFXSnS2v.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/CasinoSort-BllIwG-L.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/CasinoSort-tQyhZT1U.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.

v1.85.19

14 findings
HIGH New obfuscated file: components/CasinoFilter-ChNOJ2MK.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/CasinoGamesCategorySection-k99QzULe.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/CasinoGameThumbnail-D5aY7MyL.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/CasinoLastPlayedSection-ds7jt5iT.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/CasinoSort-Bjtm0zBv.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/CasinoFilter-aZNjaj7s.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/CasinoFilter-BTVMoy_t.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/CasinoGamesCategorySection-6xzUZp3K.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/CasinoGamesCategorySection-BHDp-KJ4.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/CasinoGameThumbnail-BRddAcBN.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/CasinoGameThumbnail-rFXSnS2v.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/CasinoSort-BllIwG-L.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/CasinoSort-tQyhZT1U.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.

v1.85.18

14 findings
HIGH New obfuscated file: components/CasinoFilter-ChNOJ2MK.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/CasinoGamesCategorySection-k99QzULe.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/CasinoGameThumbnail-D5aY7MyL.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/CasinoLastPlayedSection-ds7jt5iT.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/CasinoSort-Bjtm0zBv.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/CasinoFilter-aZNjaj7s.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/CasinoFilter-BTVMoy_t.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/CasinoGamesCategorySection-6xzUZp3K.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/CasinoGamesCategorySection-BHDp-KJ4.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/CasinoGameThumbnail-BRddAcBN.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/CasinoGameThumbnail-rFXSnS2v.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/CasinoSort-BllIwG-L.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/CasinoSort-tQyhZT1U.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.

v1.85.17

1 finding
LOW No provenance attestation provenance

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

v1.85.16

1 finding
LOW No provenance attestation provenance

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

v1.85.15

1 finding
LOW No provenance attestation provenance

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

v1.85.14

1 finding
LOW No provenance attestation provenance

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

v1.85.13

1 finding
LOW No provenance attestation provenance

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

v1.85.12

2 findings
HIGH Publisher changed: emfe_release → adrian.pripon (on 2025-11-19) provenance

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

LOW No provenance attestation provenance

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

v1.85.11

1 finding
LOW No provenance attestation provenance

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

v1.85.10

1 finding
LOW No provenance attestation provenance

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

v1.85.9

1 finding
LOW No provenance attestation provenance

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

v1.85.8

1 finding
LOW No provenance attestation provenance

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

v1.85.7

1 finding
LOW No provenance attestation provenance

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

v1.85.6

1 finding
LOW No provenance attestation provenance

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

v1.85.5

1 finding
LOW No provenance attestation provenance

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

v1.85.4

1 finding
LOW No provenance attestation provenance

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

v1.85.3

1 finding
LOW No provenance attestation provenance

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

v1.85.2

1 finding
LOW No provenance attestation provenance

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

v1.85.1

1 finding
LOW No provenance attestation provenance

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

v1.85.0

1 finding
LOW No provenance attestation provenance

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

v1.84.3

1 finding
LOW No provenance attestation provenance

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

v1.84.2

1 finding
LOW No provenance attestation provenance

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

v1.84.1

1 finding
LOW No provenance attestation provenance

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

v1.84.0

1 finding
LOW No provenance attestation provenance

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

v1.83.12

1 finding
LOW No provenance attestation provenance

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

v1.83.11

1 finding
LOW No provenance attestation provenance

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

v1.83.10

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

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.83.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.83.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.83.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.83.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.83.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.83.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.83.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.83.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.83.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.82.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.81.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.81.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.81.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.80.19

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

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

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

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

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

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

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

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

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

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

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.80.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.80.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.80.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.80.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.80.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.80.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.80.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.80.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.80.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.77.32

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

v1.77.28

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.77.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.77.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.77.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.77.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.77.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.77.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.77.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.77.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.77.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.76.14

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

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

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

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

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.