@vitest/spy
Lightweight Jest compatible spy implementation
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): Package transitioned from vitestbot to GitHub Actions CI/CD publishing with SLSA provenance attestation — a legitimate and positive supply chain improvement for the vitest ecosystem. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): yyx990803 is Evan You, creator of Vue.js and core contributor to Vite/Vitest — a legitimate maintainer addition, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): vitestbot removal is consistent with transition to GitHub Actions CI/CD publishing; the bot account is no longer needed. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @vitest/spy is a scoped package in the official vitest namespace; Levenshtein comparison to 'pg' is a false positive with no typosquat intent. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Flagged maintainers (antfu, patak, yyx990803) are well-known legitimate OSS developers; no-deps and short README are normal for this compiled utility package. | ai |
Versions (showing 44 of 144)
| Version | Deps | Published |
|---|---|---|
| 0.31.1 | 1 / 0 | |
| 0.31.0 | 1 / 0 | |
| 0.30.1 | 1 / 0 | |
| 0.30.0 | 1 / 0 | |
| 0.29.8 | 1 / 0 | |
| 0.29.7 | 1 / 0 | |
| 0.29.6 | 1 / 0 | |
| 0.29.5 | 1 / 0 | |
| 0.29.4 | 1 / 0 | |
| 0.29.3 | 1 / 0 | |
| 0.29.2 | 1 / 0 | |
| 0.29.1 | 1 / 0 | |
| 0.29.0 | 1 / 0 | |
| 0.28.5 | 1 / 0 | |
| 0.28.4 | 1 / 0 | |
| 0.28.3 | 1 / 0 | |
| 0.28.2 | 1 / 0 | |
| 0.28.1 | 1 / 0 | |
| 0.28.0 | 1 / 0 | |
| 4.1.0-beta.6 | 0 / 0 | |
| 4.1.0-beta.5 | 0 / 0 | |
| 4.1.0-beta.4 | 0 / 0 | |
| 4.1.0-beta.3 | 0 / 0 | |
| 4.1.0-beta.2 | 0 / 0 | |
| 4.1.0-beta.1 | 0 / 0 | |
| 4.0.0-beta.9 | 0 / 0 | |
| 4.0.0-beta.8 | 0 / 0 | |
| 4.0.0-beta.7 | 0 / 0 | |
| 4.0.0-beta.6 | 0 / 0 | |
| 4.0.0-beta.5 | 1 / 0 | |
| 4.0.0-beta.4 | 1 / 0 | |
| 4.0.0-beta.3 | 1 / 0 | |
| 4.0.0-beta.2 | 1 / 0 | |
| 4.0.0-beta.19 | 0 / 0 | |
| 4.0.0-beta.18 | 0 / 0 | |
| 4.0.0-beta.17 | 0 / 0 | |
| 4.0.0-beta.16 | 0 / 0 | |
| 4.0.0-beta.15 | 0 / 0 | |
| 4.0.0-beta.14 | 0 / 0 | |
| 4.0.0-beta.13 | 0 / 0 | |
| 4.0.0-beta.12 | 0 / 0 | |
| 4.0.0-beta.11 | 0 / 0 | |
| 4.0.0-beta.10 | 0 / 0 | |
| 4.0.0-beta.1 | 1 / 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.
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.