@vercel/cli-support@65.3.1
⚠ Under reviewThe JavaScript Vercel CLI, installed by `vercel` where no native binary is available
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe inspected code shows Vercel-aligned authentication and CLI setup behavior, without evidence of an attack. The agent-configuration behavior and broader runtime paths remain unresolved, so a clean or warning verdict is not supported by this inspection.
Decision evidence
public snapshot- package.json identifies this as Vercel's JavaScript CLI package.
- The inspected plugin code reads Claude's installed-plugin registry; the excerpt does not establish what other setup code changes.
- The inspected core excerpt writes Vercel best-practices content to a target file, but does not establish how that target is selected or how the command is activated.
- The inspected AI setup path can recover a saved key, while the shown output path prints a newly created key only under specific conditions.
- The inspected OIDC refresh sends a bearer token to the Vercel API; the OpenAPI SSO request sends a Vercel token in a cookie to the SSO endpoint.
- The reviewed excerpts do not establish credential transfer to an unrelated recipient or unconsented installation-time behavior.
Source & flagged code
12 flaggedPackage contains a critical-looking secret pattern.
dist/commands-blob.jsView on unpkg · L8Findings
Affected versions and remediation
This report applies to @vercel/cli-support@65.3.1.
See all versions of @vercel/cli-support for other recorded verdicts.
- Review the evidence and your use of @vercel/cli-support@65.3.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.