@mastra/vercel
Vercel serverless sandbox provider for Mastra workspaces
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation; missing gitHead is consistent with CI/CD publish workflow change, not a supply chain risk. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Published by GitHub Actions with SLSA attestation; maintainer removal reflects CI/CD-only workflow migration for this package. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Mastra monorepo consistently uses 0.0.0 as workspace placeholder version; not indicative of malice. | ai | |
| typosquat | typosquat.levenshtein:parcel | AI (typosquat): Scoped @mastra/* package in the official mastra-ai monorepo; no relation to 'parcel'. | ai |
v0.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.