@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 29 of 129)
| Version | Deps | Published |
|---|---|---|
| 0.31.1 | 3 / 3 | |
| 0.31.0 | 3 / 3 | |
| 0.30.1 | 3 / 3 | |
| 0.30.0 | 3 / 3 | |
| 4.1.0-beta.6 | 4 / 2 | |
| 4.1.0-beta.5 | 4 / 2 | |
| 4.1.0-beta.4 | 4 / 2 | |
| 4.1.0-beta.3 | 3 / 3 | |
| 4.1.0-beta.2 | 3 / 3 | |
| 4.1.0-beta.1 | 3 / 3 | |
| 4.0.0-beta.9 | 3 / 3 | |
| 4.0.0-beta.8 | 3 / 3 | |
| 4.0.0-beta.7 | 3 / 3 | |
| 4.0.0-beta.6 | 3 / 3 | |
| 4.0.0-beta.5 | 3 / 3 | |
| 4.0.0-beta.4 | 3 / 3 | |
| 4.0.0-beta.3 | 3 / 3 | |
| 4.0.0-beta.2 | 3 / 3 | |
| 4.0.0-beta.19 | 3 / 3 | |
| 4.0.0-beta.18 | 3 / 3 | |
| 4.0.0-beta.17 | 3 / 3 | |
| 4.0.0-beta.16 | 3 / 3 | |
| 4.0.0-beta.15 | 3 / 3 | |
| 4.0.0-beta.14 | 3 / 3 | |
| 4.0.0-beta.13 | 3 / 3 | |
| 4.0.0-beta.12 | 3 / 3 | |
| 4.0.0-beta.11 | 3 / 3 | |
| 4.0.0-beta.10 | 3 / 3 | |
| 4.0.0-beta.1 | 3 / 3 |
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.
v4.1.0-beta.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0-beta.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0-beta.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0-beta.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0-beta.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0-beta.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.9
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-08-26. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0-beta.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.14
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-10-01. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0-beta.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0-beta.10
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-09-01. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0-beta.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.