@vitest/snapshot
Vitest snapshot manager
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 project automation account; publisher transition from oreanno to vitestbot reflects legitimate move to bot-based CI publishing for the vitest-dev org. | ai | |
| dependencies | unvetted-dep:@vitest/utils | AI (dependencies): @vitest/utils is a sibling package in the same vitest-dev/vitest monorepo, pinned to the same version. This dependency is expected and benign. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Spam flags on patak, antfu, vitestbot, oreanno are false positives; these are well-known maintainers of the legitimate Vitest open-source project. | ai |
Versions (showing 100 of 129)
| Version | Deps | Published |
|---|---|---|
| 4.1.7 | 4 / 2 | |
| 4.1.6 | 4 / 2 | |
| 4.1.5 | 4 / 2 | |
| 4.1.4 | 4 / 2 | |
| 4.1.3 | 4 / 2 | |
| 4.1.2 | 4 / 2 | |
| 4.1.1 | 4 / 2 | |
| 4.1.0 | 4 / 2 | |
| 4.0.18 | 3 / 3 | |
| 4.0.17 | 3 / 3 | |
| 4.0.16 | 3 / 3 | |
| 4.0.15 | 3 / 3 | |
| 4.0.14 | 3 / 3 | |
| 4.0.13 | 3 / 3 | |
| 4.0.12 | 3 / 3 | |
| 4.0.11 | 3 / 3 | |
| 4.0.10 | 3 / 3 | |
| 4.0.9 | 3 / 3 | |
| 4.0.8 | 3 / 3 | |
| 4.0.7 | 3 / 3 | |
| 4.0.6 | 3 / 3 | |
| 4.0.5 | 3 / 3 | |
| 4.0.4 | 3 / 3 | |
| 4.0.3 | 3 / 3 | |
| 4.0.2 | 3 / 3 | |
| 4.0.1 | 3 / 3 | |
| 4.0.0 | 3 / 3 | |
| 3.2.4 | 3 / 3 | |
| 3.2.3 | 3 / 3 | |
| 3.2.2 | 3 / 3 | |
| 3.2.1 | 3 / 3 | |
| 3.2.0 | 3 / 3 | |
| 3.1.4 | 3 / 3 | |
| 3.1.3 | 3 / 3 | |
| 3.1.2 | 3 / 3 | |
| 3.1.1 | 3 / 3 | |
| 3.1.0 | 3 / 3 | |
| 3.0.9 | 3 / 3 | |
| 3.0.8 | 3 / 3 | |
| 3.0.7 | 3 / 3 | |
| 3.0.6 | 3 / 3 | |
| 3.0.5 | 3 / 3 | |
| 3.0.4 | 3 / 3 | |
| 3.0.3 | 3 / 3 | |
| 3.0.2 | 3 / 3 | |
| 3.0.1 | 3 / 3 | |
| 3.0.0 | 3 / 3 | |
| 2.1.9 | 3 / 3 | |
| 2.1.8 | 3 / 3 | |
| 2.1.7 | 3 / 3 | |
| 2.1.6 | 3 / 3 | |
| 2.1.5 | 3 / 3 | |
| 2.1.4 | 3 / 3 | |
| 2.1.3 | 3 / 3 | |
| 2.1.2 | 3 / 3 | |
| 2.1.1 | 3 / 3 | |
| 2.1.0 | 3 / 3 | |
| 2.0.5 | 3 / 3 | |
| 2.0.4 | 3 / 3 | |
| 2.0.3 | 3 / 3 | |
| 2.0.2 | 3 / 3 | |
| 2.0.1 | 3 / 3 | |
| 2.0.0 | 3 / 3 | |
| 1.6.1 | 3 / 3 | |
| 1.6.0 | 3 / 3 | |
| 1.5.3 | 3 / 3 | |
| 1.5.2 | 3 / 3 | |
| 1.5.1 | 3 / 3 | |
| 1.5.0 | 3 / 3 | |
| 1.4.0 | 3 / 3 | |
| 1.3.1 | 3 / 3 | |
| 1.3.0 | 3 / 3 | |
| 1.2.2 | 3 / 3 | |
| 1.2.1 | 3 / 3 | |
| 1.2.0 | 3 / 3 | |
| 1.1.3 | 3 / 3 | |
| 1.1.2 | 3 / 3 | |
| 1.1.1 | 3 / 3 | |
| 1.1.0 | 3 / 3 | |
| 1.0.4 | 3 / 3 | |
| 1.0.3 | 3 / 3 | |
| 1.0.2 | 3 / 3 | |
| 1.0.1 | 3 / 3 | |
| 1.0.0 | 3 / 3 | |
| 0.34.6 | 3 / 3 | |
| 0.34.5 | 3 / 3 | |
| 0.34.4 | 3 / 3 | |
| 0.34.3 | 3 / 3 | |
| 0.34.2 | 3 / 3 | |
| 0.34.1 | 3 / 3 | |
| 0.34.0 | 3 / 3 | |
| 0.33.0 | 3 / 3 | |
| 0.32.4 | 3 / 3 | |
| 0.32.3 | 3 / 3 | |
| 0.32.2 | 3 / 3 | |
| 0.32.1 | 3 / 3 | |
| 0.32.0 | 3 / 3 | |
| 0.31.4 | 3 / 3 | |
| 0.31.3 | 3 / 3 | |
| 0.31.2 | 3 / 3 |
v4.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.