@vercel/cli-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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): zeit-bot is a known Vercel automation account; addition is consistent with org-wide bot consolidation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Mass removal reflects Vercel org maintainer list cleanup, not a takeover; SLSA provenance confirms legitimate CI publish. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Vercel utility package; sparse README and no keywords are expected for org-internal tooling. | ai | |
| email-domain | unclaimed-email:magic.io | AI (email-domain): Package has SLSA provenance from GitHub Actions and is part of the official vercel/vercel monorepo; stale maintainer email is low risk here. | ai |
v0.1.2
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.1.1
2 findingsMaintainer email '[email protected]' uses domain 'magic.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
2 findingsMaintainer email '[email protected]' uses domain 'magic.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.