The command-line interface for Vercel
84%
Total Score
healthy
Frequent releases and active, broad maintenance outweigh workflow-audit and provenance gaps.
The package has no build attestation, so consumers receive less independently verifiable publication evidence despite the trusted publisher identity being GitHub.
The audit analyzed all 24 workflows and found no untrusted checkout or script-injection cases, but 75 of 156 action references are unpinned, one file failed analysis, and high-confidence template-injection findings remain; these are workflow hygiene concerns rather than demonstrated release risk here.
| Title | Versions | Severity |
|---|---|---|
CVE-2026-44479 vercel is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in versions 50.16.0 - 52.0.0. | 50.16.0 - 52.0.0 | Medium |
| Dependency | Last Release | Score |
|---|---|---|
zod Version 4.1.11 | — | — |
jose Version 5.9.6 | — | — |
uuid Version 14.0.1 | — | — |
luxon Version ^3.4.0 | — | — |
undici Version 5.29.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.