@ai-sdk/test-server
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): Transition from vercel-release-bot to GitHub Actions is a CI pipeline change, backed by SLSA provenance attestation from the vercel/ai repo. | ai | |
| dependencies | unvetted-dep:msw | AI (dependencies): msw is a well-established HTTP mocking library; its use in @ai-sdk/test-server (a test utility) is expected and appropriate. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): jaredpalmer's removal is consistent with Vercel consolidating publishing under vercel-release-bot; not a takeover signal for this org-owned package. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop explained by refactoring to delegate to msw as a runtime dep rather than bundling custom server code; expected for a test utility package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.0.5 | 1 / 4 | |
| 1.0.4 | 1 / 4 | |
| 1.0.3 | 1 / 4 | |
| 1.0.2 | 1 / 4 | |
| 1.0.1 | 1 / 4 | |
| 1.0.0 | 1 / 4 | |
| 0.0.4 | 1 / 4 | |
| 0.0.3 | 1 / 4 | |
| 0.0.2 | 1 / 4 | |
| 0.0.1 | 1 / 4 |
v1.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-04-30. 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.
v1.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-04-29. 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.
v0.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-04-30. 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.
v0.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-04-29. 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.