@vercel/cli-support@65.4.0
⚠ 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 source excerpts do not substantiate the scanner’s host-fingerprint or credential-exfiltration claims. Required runtime callers and the complete citation coverage set remain unresolved, so the package cannot be cleared or blocked on this inspection.
Decision evidence
public snapshot- The manifest identifies the package and version; inspected metadata shows no lifecycle hooks in the excerpted portion.
- The inspected OIDC helper sends an authentication token to the Vercel API for an OIDC token refresh.
- The inspected agent-related excerpts read Claude’s installed-plugin registry and update Vercel best-practices content.
- The cited excerpts do not establish host-identity collection or credential transfer to an unrelated recipient.
- The inspected code does not establish unconsented agent configuration changes.
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.4.0.
See all versions of @vercel/cli-support for other recorded verdicts.
- Review the evidence and your use of @vercel/cli-support@65.4.0 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.