@vitest/ui
UI for Vitest
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/client/assets/index-BLZJq7cG.js | AI (source-diff): Minified Vite build output for the UI client; expected for this package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-_g5qy0bI.js | AI (source-diff): Minified Vite+Vue client bundle; expected for this UI package's dist/client/assets output. | ai | |
| phantom-deps | phantom-dep:vue-virtual-scroller | AI (phantom-deps): Listed as a runtime dependency in package.json; used in the bundled client UI, not directly imported in Node entry. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Official Vitest scoped package; false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Official Vitest scoped package; false positive. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Official Vitest scoped package; Levenshtein match against short names is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Official Vitest scoped package; false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Official Vitest scoped package; false positive. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DaKof6xz.js | AI (source-diff): Vite-bundled client UI asset; minified Vue app is expected for this package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-BPQdrqGZ.js | AI (source-diff): Vite-bundled client SPA asset; minification is expected for this package's browser UI. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-Cil7RPEC.js | AI (source-diff): This is standard Vite-bundled/minified frontend JS for the UI package. Sample shows Vue 3 internals with copyright headers — minified, not obfuscated. Expected build artifact for @vitest/ui. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-CBcuRGkf.js | AI (source-diff): @vitest/ui ships a Vite-built browser UI bundle; minified client assets with long lines are expected output, not obfuscation. SLSA provenance confirms CI build integrity. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-Co-EY0lY.js | AI (source-diff): @vitest/ui ships a Vite-bundled client UI; minified JS bundles are expected and the sample shows standard Vue 3 internals, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DYFYwZ2-.js | AI (source-diff): This is standard Vite/Rollup minified Vue SPA output for the UI client bundle. The sample shows recognizable Vue 3 internals with license headers — not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-B3LybwKR.js | AI (source-diff): @vitest/ui ships a Vite-built client SPA; minified/hashed bundle files in dist/client/assets/ are expected build artifacts, not obfuscation. SLSA provenance confirms CI/CD origin. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): yyx990803 is Evan You (Vue/Vite creator), a core ecosystem contributor. Addition is expected and legitimate for this package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DalB9Rpk.js | AI (source-diff): @vitest/ui ships a Vite-built frontend bundle; hashed asset files in dist/client/assets/ are standard minified output, not obfuscation. Pattern is stable across all versions. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-YGltZS-e.js | AI (source-diff): This is standard Vite/Rollup-minified frontend bundle output for the @vitest/ui web client. Contains recognizable Vue 3 source with proper license headers. SLSA provenance confirms CI-built artifact. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-BjtzXzAw.js | AI (source-diff): @vitest/ui ships a Vite-built frontend bundle; minified JS in dist/client/assets/ is expected build output, not obfuscation. Stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-BcP0bNv8.js | AI (source-diff): @vitest/ui ships a Vite-bundled frontend client; minified JS assets in dist/client/assets/ are expected build artifacts, not obfuscation. Pattern is stable across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-CPanfHPD.js | AI (source-diff): @vitest/ui ships a Vite-built frontend bundle; minified client assets are expected and normal for this package. Sample confirms legitimate Vue/Vite framework code. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-CR4OJGrW.js | AI (source-diff): @vitest/ui always ships a minified Vite/Vue client bundle in dist/client/assets/; long lines are standard build output, not obfuscation. Stable pattern across all 345 versions. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-vKQ25zpc.js | AI (source-diff): @vitest/ui ships a Vite-bundled SPA; large minified JS assets in dist/client/assets/ are expected and normal for this package. Sample confirms standard Vue/Vite bundle content. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DHXSWiHD.js | AI (source-diff): @vitest/ui ships a Vite-built frontend bundle; minified JS assets in dist/client/assets/ are expected build artifacts, not obfuscation. Pattern is stable across versions. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DWjHzG4O.js | AI (source-diff): Minified frontend bundle is expected for @vitest/ui — it ships a built Vite/Vue client app. Sample shows standard Vue/Vite boilerplate, not malicious code. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-Cv3XDLXs.js | AI (source-diff): @vitest/ui ships a Vite-bundled frontend client; minified JS assets are expected and the sample shows standard Vue 3 framework code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-CsZqQx26.js | AI (source-diff): @vitest/ui ships a pre-built Vite/Vue frontend; minified JS bundles in dist/client/assets/ are expected build output, not obfuscation. SLSA provenance confirms CI build. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-BAYvVM30.js | AI (source-diff): @vitest/ui ships a Vite-built Vue frontend bundle; minified/content-hashed JS files in dist/client/assets/ are expected build artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-aqqnYS46.js | AI (source-diff): @vitest/ui ships a pre-built Vite/Vue SPA client bundle; minified JS assets are expected in every release. The sample shows standard Vue 3 internals, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-BX_iUIjH.js | AI (source-diff): @vitest/ui ships a Vite-built frontend bundle; minified JS assets are expected build outputs, not obfuscation. SLSA provenance confirms CI/CD build integrity. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-CkLwJNkP.js | AI (source-diff): @vitest/ui ships a pre-built Vite web client; minified JS bundles in dist/client/assets/ are expected build artifacts, not malicious obfuscation. SLSA provenance confirms CI/CD build integrity. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-D_ryMEPs.js | AI (source-diff): @vitest/ui ships Vite-bundled minified frontend assets in every release; long-line minified JS is expected and the sample shows standard Vue/JS code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-CLLxNdKA.js | AI (source-diff): This is a standard Vite-minified frontend bundle for the vitest UI. Long lines are minification artifacts; the sample shows recognizable Vue 3 source with proper license headers. Expected for this package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-BUCFJtth.js | AI (source-diff): This is a Vite-bundled minified frontend JS asset for the vitest UI client. The sample shows standard Vue 3 framework code with license headers — minification, not obfuscation. Expected for this package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DnyN8l5D.js | AI (source-diff): @vitest/ui ships a Vite-built web UI client; large minified JS bundles with content-hash filenames are the expected build output, not obfuscation. Pattern is stable across all versions. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-CfDzoXo3.js | AI (source-diff): This is a standard Vite-minified frontend bundle for the vitest UI. The sample shows readable Vue 3 code with license headers — minified, not obfuscated. Expected build artifact for this package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-Di71CKDo.js | AI (source-diff): @vitest/ui ships a pre-built Vite/Vue web app; minified JS bundles are expected build artifacts. Sample confirms standard Vue 3 framework code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-zBMt7UWw.js | AI (source-diff): @vitest/ui ships a Vite-built SPA client bundle; minified JS with long lines is expected and the sample shows legitimate Vue 3 internals, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-TGTX-jRo.js | AI (source-diff): This is a Vite-bundled Vue SPA client asset. Content-hashed filenames and minified JS are expected build artifacts for @vitest/ui's frontend. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DflzHTY2.js | AI (source-diff): Large minified JS files are expected build artifacts for @vitest/ui's Vite-built frontend bundle. Content-hashed filenames change with each build. Sample shows legitimate Vue/browser code. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DYO2mJ8d.js | AI (source-diff): This is standard Vite-minified frontend bundle output for the Vitest UI SPA. Long lines are minification artifacts, not obfuscation. Vue internals are clearly visible in the sample. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-DZIaN7GU.js | AI (source-diff): @vitest/ui ships a Vite-built web UI; minified client bundles with long lines are expected build artifacts, not obfuscation. Pattern is stable across all versions of this package. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-C5TM4_dj.js | AI (source-diff): @vitest/ui ships a Vite-built Vue SPA client; minified/hashed bundle files are expected build artifacts, not obfuscation. SLSA provenance confirms CI/CD origin. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-Dpc7kNBC.js | AI (source-diff): @vitest/ui ships a compiled Vite web app frontend; minified JS bundles in dist/client/assets/ are expected build artifacts, not obfuscation. SLSA provenance confirms CI/CD integrity. | ai | |
| source-diff | obfuscated-file:dist/client/assets/index-l1rdxr0p.js | AI (source-diff): @vitest/ui ships a pre-built Vite/Vue SPA; large minified client bundles are expected build artifacts, not obfuscation. Pattern is stable across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Flagged maintainers (antfu, patak, yyx990803, vitestbot) are prominent Vue/Vite ecosystem authors, not spam. False positive for this package. | ai | |
| phantom-deps | phantom-dep:@vitest/utils | AI (phantom-deps): Sibling monorepo package loaded by convention/framework internals; phantom-dep detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:fflate | AI (phantom-deps): fflate is a declared runtime dependency used in the built client bundle; phantom-dep false positive for bundled packages. | ai |
Versions (showing 100 of 284)
| Version | Deps | Published |
|---|---|---|
| 0.30.1 | 7 / 27 | |
| 0.30.0 | 7 / 27 | |
| 0.29.8 | 5 / 29 | |
| 0.29.7 | 5 / 29 | |
| 0.29.6 | 5 / 29 | |
| 0.29.5 | 5 / 29 | |
| 0.29.4 | 5 / 29 | |
| 0.29.3 | 5 / 29 | |
| 0.29.2 | 5 / 29 | |
| 0.29.1 | 5 / 29 | |
| 0.29.0 | 5 / 29 | |
| 0.28.5 | 5 / 29 | |
| 0.28.4 | 5 / 29 | |
| 0.28.3 | 5 / 29 | |
| 0.28.2 | 5 / 29 | |
| 0.28.1 | 5 / 29 | |
| 0.28.0 | 5 / 29 | |
| 0.27.3 | 3 / 29 | |
| 0.27.2 | 3 / 29 | |
| 0.27.1 | 3 / 29 | |
| 0.27.0 | 3 / 29 | |
| 0.26.3 | 3 / 29 | |
| 0.26.2 | 3 / 29 | |
| 0.26.1 | 3 / 29 | |
| 0.26.0 | 3 / 29 | |
| 0.25.8 | 1 / 30 | |
| 0.25.7 | 1 / 30 | |
| 0.25.6 | 1 / 30 | |
| 0.25.5 | 1 / 30 | |
| 0.25.4 | 1 / 29 | |
| 0.25.3 | 1 / 29 | |
| 0.25.2 | 1 / 29 | |
| 0.25.1 | 1 / 29 | |
| 0.25.0 | 1 / 29 | |
| 0.24.5 | 1 / 29 | |
| 0.24.4 | 1 / 29 | |
| 0.24.3 | 1 / 29 | |
| 0.24.2 | 1 / 29 | |
| 0.24.1 | 1 / 29 | |
| 0.24.0 | 1 / 29 | |
| 0.23.4 | 1 / 29 | |
| 0.23.2 | 1 / 29 | |
| 0.23.1 | 1 / 29 | |
| 0.23.0 | 1 / 29 | |
| 0.22.1 | 1 / 29 | |
| 0.22.0 | 1 / 29 | |
| 0.21.1 | 1 / 29 | |
| 0.21.0 | 1 / 29 | |
| 0.20.3 | 1 / 29 | |
| 0.20.2 | 1 / 29 | |
| 0.20.1 | 1 / 29 | |
| 0.20.0 | 1 / 29 | |
| 0.19.1 | 1 / 29 | |
| 0.19.0 | 1 / 29 | |
| 0.18.1 | 1 / 29 | |
| 0.18.0 | 1 / 31 | |
| 0.17.1 | 1 / 31 | |
| 0.17.0 | 1 / 31 | |
| 0.16.0 | 1 / 30 | |
| 0.15.2 | 1 / 30 | |
| 0.15.1 | 1 / 30 | |
| 0.15.0 | 1 / 30 | |
| 0.14.2 | 1 / 30 | |
| 0.14.1 | 1 / 30 | |
| 0.14.0 | 1 / 30 | |
| 0.13.1 | 1 / 30 | |
| 0.13.0 | 1 / 30 | |
| 0.12.10 | 1 / 30 | |
| 0.12.9 | 1 / 32 | |
| 0.12.8 | 1 / 32 | |
| 0.12.7 | 1 / 32 | |
| 0.12.6 | 1 / 32 | |
| 0.12.5 | 1 / 32 | |
| 0.12.4 | 1 / 32 | |
| 0.12.3 | 1 / 32 | |
| 0.12.2 | 1 / 32 | |
| 0.12.1 | 1 / 32 | |
| 0.12.0 | 1 / 32 | |
| 0.11.0 | 1 / 32 | |
| 0.10.5 | 1 / 32 | |
| 0.10.4 | 1 / 32 | |
| 0.10.3 | 1 / 32 | |
| 0.10.2 | 1 / 32 | |
| 0.10.1 | 1 / 32 | |
| 0.10.0 | 1 / 32 | |
| 0.9.4 | 1 / 32 | |
| 0.9.3 | 1 / 32 | |
| 0.9.2 | 1 / 31 | |
| 0.9.1 | 1 / 31 | |
| 0.9.0 | 1 / 30 | |
| 0.8.5 | 1 / 30 | |
| 0.8.4 | 1 / 30 | |
| 0.8.3 | 1 / 30 | |
| 0.8.2 | 1 / 30 | |
| 0.8.1 | 1 / 30 | |
| 0.8.0 | 1 / 30 | |
| 0.7.13 | 1 / 30 | |
| 0.7.12 | 1 / 30 | |
| 0.7.11 | 1 / 30 | |
| 0.7.10 | 1 / 30 |
v0.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.