Vercel Tool

• Outcome: Pass
• Latest audit: May 29, 2026, 8:40 PM
• Version:
  1.1.0

Overview

This skill transparently generates Vercel administration commands for the user to review and run, but users should treat rollback, tokens, and environment-variable access carefully.

Install only if you intend to administer Vercel projects with generated commands. Review every command before running it, treat rollback as a live production change, use the least-privileged Vercel token available, and avoid pasting tokens or environment output into shared chats or logs.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (5)

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The trigger phrases are broad and overlap with common operational requests such as 'build logs', 'environment variables', and 'vercel deploy'. That makes accidental activation more likely, which is risky because this skill can surface sensitive operational data and generate commands for state-changing actions like rollback and deployment.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The rollback command can change production state by promoting a previous deployment, but the skill text does not warn the user about the operational impact or require confirmation. In deployment tooling, missing friction around rollback increases the chance of accidental or rushed production changes, potentially causing outages, reversions of security fixes, or data/API incompatibilities.

Missing User Warnings

Medium

• Confidence: 96% confidence
• Finding: Listing environment variables is a sensitive operation because environment configuration often contains secrets, tokens, internal hostnames, and other confidential values. Without a privacy warning, users may invoke the command in inappropriate contexts or expose sensitive data in logs, transcripts, or shared terminals.

Missing User Warnings

Medium

• Confidence: 87% confidence
• Finding: The rollback command generates a production-affecting API request without any warning, confirmation step, or explanation of consequences. In a deployment-management context, a user may run it and unintentionally promote an older deployment, causing outages, regressions, or rollback of security fixes.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The instructions recommend placing a long-lived Vercel API token in a shell profile without warning that this is sensitive credential material. Persistent storage in ~/.bashrc or ~/.zshrc increases exposure through local compromise, accidental disclosure, backups, dotfile sync, or screen sharing, especially since the token can control deployments and access project metadata.

VirusTotal

67/67 vendors flagged this skill as clean.