← Home

@everymatrix/player-gaming-history

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

clokzeoleksandr.v.stepanovtaras.maksymivnatalya.anisimovaemfe_releaserayiispmariana.gheorgheadrian.priponandriizadvirnyiraulvasileemstefan.vladgoe.sutadarie.tisaianustefanaotong.woodtikarncatalinpoclidcristi.ungureanumaria.bumbar1liviuclement.everymatrixmihaibalanfrankie24

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:components/PlayerGamingHistory-CUzAxWEX.js AI (source-diff): Bundled svelte runtime; no fetched/executed remote payload. ai
source-diff obfuscated-file:components/PlayerAccountGamingLimitsGroupEdit-BEuEPUET.js AI (source-diff): Bundled Vite/Rollup output, not true obfuscation. ai
source-diff net-exec-file:components/PlayerGamingHistory-DQsYtBso.js AI (source-diff): Bundled svelte runtime; no fetched/executed remote payload. ai
phantom-deps phantom-dep:cross-env AI (phantom-deps): Used in build/dev scripts only. ai
phantom-deps phantom-dep:sirv-cli AI (phantom-deps): Used via 'start' script, not source import; standard dev tool. ai
phantom-deps phantom-dep:@vaadin/vaadin-date-picker AI (phantom-deps): Likely used in svelte template markup, not JS import. ai
phantom-deps phantom-dep:svelte AI (phantom-deps): Framework referenced via config/svelte field. ai
source-diff obfuscated-file:components/PlayerGamingHistory-BLk2WYYM.cjs AI (source-diff): Bundled Svelte/Vaadin component output, not true obfuscation. ai
source-diff net-exec-file:components/PlayerGamingHistory-BLk2WYYM.cjs AI (source-diff): Bundled framework code with fetch+Function, not a loader/dropper. ai
source-diff net-exec-file:components/PlayerGamingHistory-DAhQYl3h.cjs AI (source-diff): Bundler dynamic-import pattern, no exfil/fetch-exec behavior found. ai
source-diff obfuscated-file:components/PlayerGamingHistory-DAhQYl3h.cjs AI (source-diff): Bundled Svelte component output, not true obfuscation. ai
source-diff net-exec-file:components/PlayerGamingHistory-CjQtIh-n.js AI (source-diff): Same bundled dev-mode helper pattern as sibling file. ai
source-diff net-exec-file:components/PlayerGamingHistory-fXqpl1eg.cjs AI (source-diff): Same bundled dev-mode helper pattern, cjs build output. ai
source-diff net-exec-file:components/PlayerGamingHistory-BybKqTVn.js AI (source-diff): Standard bundled runtime code, no evidence of dropper behavior. ai
source-diff obfuscated-file:components/PlayerGamingHistory-BybKqTVn.js AI (source-diff): Bundled Svelte/rollup output, not obfuscation; recurring pattern in this component library. ai
npm-metadata no-description AI (npm-metadata): Internal component package, consistently missing description across versions. ai
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/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
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
semgrep semgrep:new-function-constructor AI (semgrep): Fires inside Vaadin dev-mode detection boilerplate; stable false positive for this component package. 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

Versions (showing 100 of 660)

Version Deps Published
1.54.6 0 / 0
1.54.4 0 / 0
1.54.2 0 / 0
1.54.0 1 / 0
1.53.12 0 / 0
1.53.11 0 / 0
1.53.10 0 / 0
1.53.0 1 / 0
1.52.6 1 / 0
1.52.5 1 / 0
1.52.4 1 / 0
1.52.3 1 / 0
1.52.2 1 / 0
1.52.1 1 / 0
1.52.0 1 / 0
1.51.0 1 / 0
1.50.1 1 / 0
1.50.0 1 / 0
1.49.2 1 / 0
1.49.1 1 / 0
1.49.0 1 / 0
1.48.2 1 / 0
1.48.1 1 / 0
1.48.0 1 / 0
1.47.3 1 / 0
1.47.2 1 / 0
1.47.1 1 / 0
1.47.0 1 / 0
1.46.1 1 / 0
1.46.0 1 / 0
1.45.14 1 / 0
1.45.13 1 / 0
1.45.11 1 / 0
1.45.10 1 / 0
1.45.9 1 / 0
1.45.8 1 / 0
1.45.7 1 / 0
1.45.6 1 / 0
1.45.5 1 / 0
1.45.4 1 / 0
1.45.3 1 / 0
1.45.2 1 / 0
1.45.0 1 / 0
1.44.0 3 / 15
1.43.4 3 / 15
1.43.3 3 / 15
1.43.2 3 / 15
1.43.1 3 / 15
1.43.0 3 / 15
1.42.0 3 / 15
1.41.0 3 / 15
1.40.0 3 / 15
1.39.3 3 / 15
1.39.2 3 / 15
1.39.1 3 / 15
1.39.0 3 / 15
1.38.0 3 / 15
1.37.12 3 / 15
1.37.11 3 / 15
1.37.10 3 / 15
1.37.9 3 / 15
1.37.8 3 / 15
1.37.7 3 / 15
1.37.6 3 / 15
1.37.5 3 / 15
1.37.4 3 / 15
1.37.3 3 / 15
1.37.2 3 / 15
1.37.1 3 / 15
1.37.0 3 / 15
1.36.1 3 / 15
1.36.0 3 / 15
1.35.0 3 / 15
1.34.3 3 / 15
1.34.2 3 / 15
1.34.1 3 / 15
1.34.0 3 / 15
1.33.5 3 / 15
1.33.4 3 / 15
1.33.3 3 / 15
1.33.2 3 / 15
1.33.1 3 / 15
1.33.0 3 / 15
1.32.16 3 / 15
1.31.2 3 / 15
1.31.1 3 / 15
1.31.0 3 / 15
1.30.1 3 / 15
1.30.0 3 / 15
1.29.9 3 / 15
1.29.8 3 / 15
1.29.7 3 / 15
1.29.6 3 / 15
1.29.5 3 / 15
1.29.4 3 / 15
1.29.3 3 / 15
1.29.0 3 / 15
1.28.8 3 / 15
1.28.7 3 / 15
1.28.5 3 / 15
Showing 100 of 660 Next page →

v1.54.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.54.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.54.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.54.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.53.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.53.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.53.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.53.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.52.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.52.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.52.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.52.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.52.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.52.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.52.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.51.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.50.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.50.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.49.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.49.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.49.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.48.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.48.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.48.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.47.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.47.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.47.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.47.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.46.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.46.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.45.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.45.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.45.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.45.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.45.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.45.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.45.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.45.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.45.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.45.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.45.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.45.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.45.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.44.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.43.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.43.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.43.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.43.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.43.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.42.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.41.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.40.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.39.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.39.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.39.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.39.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.38.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.37.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.37.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.37.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.37.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.37.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.37.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.37.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.37.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.37.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.37.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.37.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.37.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.37.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.36.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.36.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.35.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.34.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.34.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.34.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.34.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.33.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.33.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.33.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.33.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.33.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.33.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.32.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.31.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.31.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.31.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.30.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.30.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.29.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.29.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.29.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.29.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.29.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.29.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.29.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.29.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.28.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.28.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.28.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.