Clovercli

• Outcome: Review
• Latest audit: May 28, 2026 at 5:03 AM UTC
• Version:
  1.0.0

Overview

This appears to be a legitimate Clover POS CLI skill, but it needs review because it asks for sensitive business credentials and documents high-impact POS operations without enough scoping or safety guidance.

Install only if you trust the external CloverCLI package and are comfortable giving it access to your Clover POS account. Use the least-privileged token available, avoid putting long-lived tokens in shell startup files, protect exported reports, confirm create/delete/raw API actions before running them, and ignore or remove the embedded known-client merchant ID.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• 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
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (4)

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: The documentation instructs users to configure long-lived access-token credentials and then demonstrates capabilities including exports, deletes, and raw API access without any caution about sensitive merchant data, destructive operations, or privacy implications. In a POS context, this can lead to accidental disclosure or modification of financial, customer, employee, and inventory data by users who are not adequately warned about the scope and sensitivity of the commands.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The documented `discounts delete <id>` command is a destructive operation presented without any warning, confirmation guidance, or note on reversibility. In a live merchant environment, this can cause accidental removal of pricing rules that affect checkout behavior, reporting consistency, and business operations.

Missing User Warnings

Medium

• Confidence: 91% confidence
• Finding: The export examples write merchant order and item data to local files without warning that the output may contain sensitive business information and may overwrite existing files. In the Clover/POS context, exported data can include commercially sensitive sales and inventory records, increasing the risk of local exposure, mishandling, or inadvertent data loss.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The raw API access section exposes a generic mechanism for calling Clover endpoints but does not warn that arbitrary endpoint use may expose highly sensitive merchant information or invoke state-changing actions depending on the method and path. Because this skill targets a POS platform with payment, customer, employee, and merchant settings data, undocumented or careless API use is more dangerous than in a low-sensitivity domain.

VirusTotal

64/64 vendors flagged this skill as clean.