@vitest/utils
Shared Vitest utility functions
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from vitestbot to GitHub Actions CI/CD with SLSA provenance is a legitimate and improved publishing flow for the vitest-dev org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): yyx990803 (Evan You) is a core member of the Vite/Vitest ecosystem; legitimate maintainer addition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): vitestbot removal coincides with move to GitHub Actions CI publishing; legitimate organizational change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long gap reflects monorepo release cadence, not account takeover; SLSA provenance confirms legitimate CI/CD publishing. | ai | |
| dependencies | unvetted-dep:convert-source-map | AI (dependencies): convert-source-map is a well-known, widely-used npm package for source map handling; not a security concern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Vitest maintainers are legitimate; empty main and minimal docs are expected for monorepo utility packages. | ai |
Versions (showing 49 of 149)
| Version | Deps | Published |
|---|---|---|
| 0.31.2 | 3 / 0 | |
| 0.31.1 | 3 / 0 | |
| 0.31.0 | 3 / 0 | |
| 0.30.1 | 3 / 0 | |
| 0.30.0 | 3 / 0 | |
| 0.29.8 | 4 / 1 | |
| 0.29.7 | 4 / 1 | |
| 0.29.6 | 4 / 1 | |
| 0.29.5 | 4 / 1 | |
| 0.29.4 | 4 / 1 | |
| 0.29.3 | 4 / 1 | |
| 0.29.2 | 5 / 1 | |
| 0.29.1 | 5 / 1 | |
| 0.29.0 | 5 / 1 | |
| 0.28.5 | 5 / 1 | |
| 0.28.4 | 5 / 1 | |
| 0.28.3 | 5 / 1 | |
| 0.28.2 | 5 / 1 | |
| 0.28.1 | 5 / 1 | |
| 0.28.0 | 5 / 1 | |
| 0.27.3 | 4 / 1 | |
| 0.27.2 | 4 / 1 | |
| 0.27.1 | 4 / 1 | |
| 0.27.0 | 4 / 1 | |
| 4.1.0-beta.6 | 3 / 5 | |
| 4.1.0-beta.5 | 3 / 5 | |
| 4.1.0-beta.4 | 2 / 4 | |
| 4.1.0-beta.3 | 2 / 5 | |
| 4.1.0-beta.2 | 2 / 5 | |
| 4.1.0-beta.1 | 2 / 5 | |
| 4.0.0-beta.9 | 3 / 4 | |
| 4.0.0-beta.8 | 3 / 4 | |
| 4.0.0-beta.7 | 3 / 4 | |
| 4.0.0-beta.6 | 3 / 4 | |
| 4.0.0-beta.5 | 3 / 4 | |
| 4.0.0-beta.4 | 3 / 4 | |
| 4.0.0-beta.3 | 3 / 4 | |
| 4.0.0-beta.2 | 3 / 4 | |
| 4.0.0-beta.19 | 2 / 5 | |
| 4.0.0-beta.18 | 2 / 5 | |
| 4.0.0-beta.17 | 2 / 5 | |
| 4.0.0-beta.16 | 2 / 5 | |
| 4.0.0-beta.15 | 2 / 5 | |
| 4.0.0-beta.14 | 2 / 5 | |
| 4.0.0-beta.13 | 2 / 5 | |
| 4.0.0-beta.12 | 2 / 5 | |
| 4.0.0-beta.11 | 2 / 5 | |
| 4.0.0-beta.10 | 3 / 4 | |
| 4.0.0-beta.1 | 3 / 4 |
v0.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
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.
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 findingsThis 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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
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.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.