@everymatrix/cashier-page
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:components/CashierPage-Db1WM6lI.cjs | AI (source-diff): Bundled Svelte component output, not obfuscation; recurring build artifact for this package. | ai | |
| source-diff | obfuscated-file:components/CashierPage-Bo-pdE3e.cjs | AI (source-diff): Bundled Svelte/Stencil component output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierCarousel-BekweMPA.cjs | AI (source-diff): Bundled build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierMethodDetails-ClsKYPK5.cjs | AI (source-diff): Bundled build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierPage-CdNfJQft.cjs | AI (source-diff): Bundled build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierPage-BL7F7z0O.cjs | AI (source-diff): Bundled build output (svelte/webpack banner), not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierError-Bi6R1tHR.cjs | AI (source-diff): Bundled Svelte/Stencil component output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierError-DDQmcXZG.cjs | AI (source-diff): Bundled Svelte/Rollup output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierMethodDetails-Dbnc7shQ.cjs | AI (source-diff): Bundled Svelte/Rollup output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierCarousel-Uqj8lOn9.cjs | AI (source-diff): Bundled Svelte/Stencil build chunk, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierPage-BFDNXgBN.cjs | AI (source-diff): Bundled Svelte build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierCarousel-B8Fa01wg.cjs | AI (source-diff): Bundled Svelte build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierMethodDetails-C35GONRH.cjs | AI (source-diff): Standard bundler minified output, not obfuscation; consistent with package's build pipeline. | ai | |
| source-diff | obfuscated-file:components/CashierPage-CnjHLKni.cjs | AI (source-diff): Bundled minified component chunk, false positive for obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierPage-D9Qaorp_.cjs | AI (source-diff): Minified bundler output (Vite/Rollup chunk), not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierCarousel-BM7TbAtM.cjs | AI (source-diff): Minified Svelte/bundler build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierPage-CyVP1RTq.js | AI (source-diff): Vite/Rollup bundled webcomponent output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierPage-Yklnwu-d.js | AI (source-diff): Vite/Rollup bundled webcomponent output, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@everymatrix/cashier-modal | AI (phantom-deps): Same-org dependencies; likely re-exported or used transitively by subcomponents. | ai | |
| phantom-deps | phantom-dep:@everymatrix/cashier-header | AI (phantom-deps): Same-org dependencies; likely re-exported or used transitively by subcomponents. | ai | |
| phantom-deps | phantom-dep:@everymatrix/cashier-methods-list | AI (phantom-deps): Same-org dependencies; likely re-exported or used transitively by subcomponents. | ai | |
| phantom-deps | phantom-dep:@everymatrix/cashier-confirm-modal | AI (phantom-deps): Same-org dependencies; likely re-exported or used transitively by subcomponents. | ai | |
| phantom-deps | phantom-dep:@everymatrix/cashier-method-details | AI (phantom-deps): Same-org dependencies; likely re-exported or used transitively by subcomponents. | ai | |
| phantom-deps | phantom-dep:@everymatrix/cashier-iframe-redirect | AI (phantom-deps): Same-org dependencies; likely re-exported or used transitively by subcomponents. | ai | |
| phantom-deps | phantom-dep:@everymatrix/cashier-error | AI (phantom-deps): Same-org dependencies; likely re-exported or used transitively by subcomponents. | ai | |
| phantom-deps | phantom-dep:sirv-cli | AI (phantom-deps): Used via 'start' script (sirv public); build tool dep. | ai | |
| phantom-deps | phantom-dep:svelte | AI (phantom-deps): Referenced in svelte config field and build tooling. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): Used directly in build/dev scripts. | ai | |
| source-diff | obfuscated-file:components/CashierPage-BLm3V5c-.cjs | AI (source-diff): Bundled/minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierMethodDetails-Ci-pWa99.cjs | AI (source-diff): Bundled/minified build output, not obfuscation; matches package's known bundler output pattern. | ai | |
| source-diff | obfuscated-file:components/CashierCarousel-DMrMmClP.cjs | AI (source-diff): Bundled Svelte/Stencil component output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierPage-CfJ553ny.cjs | AI (source-diff): Bundled Svelte/JS build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierError-DfpdiheS.cjs | AI (source-diff): Bundled Stencil/Svelte build output, not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher confirmed as known prior maintainer per provenance INFO finding. | ai | |
| source-diff | obfuscated-file:components/CashierPage-CAjB96zt.cjs | AI (source-diff): Bundled Svelte build output, not obfuscation; consistent with package's build pipeline. | ai | |
| source-diff | obfuscated-file:components/CashierPage-CRrW53ta.cjs | AI (source-diff): Bundled Svelte/rollup build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierMethodDetails-BkiZecmE.cjs | AI (source-diff): Bundled Stencil/Svelte build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:components/CashierPage-D7cZXI1W.cjs | AI (source-diff): Bundled Svelte/Stencil build output, not obfuscation; standard for this widget package. | ai | |
| source-diff | obfuscated-file:components/CashierCarousel-1mMP8tyv.cjs | AI (source-diff): Bundled Svelte/Stencil build output, not obfuscation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal maintainer roster churn for long-lived internal package. | ai | |
| source-diff | obfuscated-file:components/CashierCarousel-DXPbv83E.cjs | AI (source-diff): Minified bundler output, not obfuscation; no malicious behavior present. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Long-standing internal widget package pattern for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Metadata sparsity typical of this enterprise component package, not spam. | ai | |
| source-diff | obfuscated-file:components/CashierPage-ryHjNYo4.cjs | AI (source-diff): Minified Svelte bundle output, not true obfuscation; consistent with package's build process. | ai | |
| source-diff | obfuscated-file:components/CashierCarousel-BzlDee2_.cjs | AI (source-diff): Minified Svelte component bundle; readable i18n strings and CSS confirm legitimate UI code. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Hash-named build artifacts from Vite/Rollup; new files per release is expected for this package. | ai | |
| source-diff | obfuscated-file:components/CashierModal-BJCRBXtp.cjs | AI (source-diff): Minified Svelte component bundle; readable CSS animations confirm legitimate UI code. | ai | |
| source-diff | obfuscated-file:components/CashierMethodsList-B9M85ykR.cjs | AI (source-diff): Minified Svelte component bundle; readable i18n strings confirm legitimate UI code. | ai | |
| source-diff | obfuscated-file:components/CashierIframeRedirect-G0gXNho3.cjs | AI (source-diff): Minified Svelte component bundle; readable CSS and i18n strings confirm legitimate UI code. | ai | |
| source-diff | obfuscated-file:components/CashierHeader-DCoLHm99.cjs | AI (source-diff): Minified Svelte component bundle; readable CSS and i18n strings confirm legitimate UI code. | ai | |
| source-diff | obfuscated-file:components/CashierError-BjCp3qo9.cjs | AI (source-diff): Minified Svelte component bundle with readable error message strings. | ai | |
| source-diff | obfuscated-file:components/CashierPage-DFc7t9CJ.cjs | AI (source-diff): Standard Vite/Rollup minified Svelte bundle; consistent with this package's established build pattern. | ai | |
| source-diff | obfuscated-file:components/CashierMethodDetails-DEXZTmb3.cjs | AI (source-diff): Minified Svelte component bundle; no obfuscation indicators beyond line length. | ai |
Versions (showing 100 of 397)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 1.76.9 | 0 / 0 | |
| 1.76.8 | 0 / 0 | |
| 1.76.7 | 0 / 0 | |
| 1.76.6 | 0 / 0 | |
| 1.76.5 | 0 / 0 | |
| 1.76.4 | 0 / 0 | |
| 1.76.3 | 0 / 0 | |
| 1.76.1 | 0 / 0 | |
| 1.76.0 | 0 / 0 | |
| 1.75.1 | 0 / 0 | |
| 1.75.0 | 0 / 0 | |
| 1.74.10 | 0 / 0 | |
| 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.40 | 0 / 0 | |
| 1.72.34 | 0 / 0 | |
| 1.72.33 | 0 / 0 | |
| 1.72.32 | 0 / 0 | |
| 1.72.31 | 0 / 0 | |
| 1.72.30 | 0 / 0 | |
| 1.72.21 | 0 / 0 | |
| 1.72.20 | 0 / 0 | |
| 1.72.19 | 0 / 0 | |
| 1.72.18 | 0 / 0 | |
| 1.72.17 | 0 / 0 | |
| 1.72.16 | 0 / 0 | |
| 1.72.15 | 0 / 0 | |
| 1.72.14 | 0 / 0 | |
| 1.72.13 | 0 / 0 | |
| 1.72.12 | 0 / 0 | |
| 1.72.11 | 0 / 0 | |
| 1.72.10 | 0 / 0 | |
| 1.72.2 | 0 / 0 | |
| 1.72.1 | 0 / 0 |
v1.80.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.13
33 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (emfe_release) than the most recent previously approved version (adrian.pripon) on 2025-10-21, but emfe_release 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.80.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.75.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.