@vitest/runner
Vitest test runner
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): vitestbot is the official vitest release bot account; publisher change from oreanno to vitestbot reflects a legitimate transition to automated CI releases, confirmed by SLSA provenance attestation. | ai | |
| dependencies | unvetted-dep:@vitest/utils | AI (dependencies): @vitest/utils is a sibling package in the same Vitest monorepo, pinned to the exact same version. Standard monorepo dependency pattern, not a risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): patak, antfu, vitestbot, oreanno are legitimate well-known maintainers of the vitest/vite ecosystem; spam flag is a false positive. README/keywords signals are irrelevant for this core vitest sub-package. | ai |
Versions (showing 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 0.31.1 | 4 / 0 | |
| 0.31.0 | 4 / 0 | |
| 0.30.1 | 4 / 0 | |
| 0.30.0 | 4 / 0 | |
| 0.29.8 | 3 / 0 | |
| 0.29.7 | 3 / 0 | |
| 0.29.6 | 3 / 0 | |
| 0.29.5 | 3 / 0 | |
| 0.29.4 | 3 / 0 | |
| 0.29.3 | 3 / 0 | |
| 0.29.2 | 3 / 0 | |
| 0.29.1 | 3 / 0 | |
| 0.29.0 | 3 / 0 | |
| 0.28.5 | 3 / 0 | |
| 0.28.4 | 3 / 0 | |
| 0.28.3 | 3 / 0 | |
| 0.28.2 | 3 / 0 | |
| 0.28.1 | 3 / 0 | |
| 0.28.0 | 3 / 0 |
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.