@vercel/static-config
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): Vercel migrated from bot account to GitHub Actions CI; same org, SLSA attested. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Stable monorepo utility; long gaps between publishes are normal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo package; missing description is cosmetic. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.4.0 | 3 / 3 | |
| 3.3.0 | 3 / 4 | |
| 3.2.0 | 3 / 5 | |
| 3.1.2 | 3 / 5 | |
| 3.1.1 | 3 / 5 | |
| 3.1.0 | 3 / 5 |
v3.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.0
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.
v3.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.