uv-troubleshooting
Audited by Socket on Feb 24, 2026
1 alert found:
Malware[Skill Scanner] Destructive bash command detected (rm -rf, chmod 777) All findings: [CRITICAL] command_injection: Destructive bash command detected (rm -rf, chmod 777) (CI004) [AITech 9.1.4] [CRITICAL] command_injection: Pipe-to-shell or eval pattern detected (CI013) [AITech 9.1.4] [CRITICAL] command_injection: URL pointing to executable file detected (CI010) [AITech 9.1.4] [CRITICAL] command_injection: Pipe-to-shell or eval pattern detected (CI013) [AITech 9.1.4] [CRITICAL] command_injection: URL pointing to executable file detected (CI010) [AITech 9.1.4] [CRITICAL] command_injection: Pipe-to-shell or eval pattern detected (CI013) [AITech 9.1.4] [CRITICAL] command_injection: URL pointing to executable file detected (CI010) [AITech 9.1.4] [HIGH] supply_chain: Reference to external script with install/setup context (SC005) This SKILL.md is a coherent troubleshooting guide for the 'uv' package manager and its capabilities align with the instructions given. However, the document repeatedly recommends high-risk supply-chain actions (curl|bash installer, unpinned 'latest' image pulls, and direct rm -rf of cache directories) without guidance on verification (checksums/signatures) or safer alternatives. There is no direct evidence of malware inside this text, but following its install instructions could lead to executing arbitrary remote code if the referenced remote artifacts are compromised. Recommend treating the installation instructions as potentially risky and prefer pinned artifacts, verified checksums, or official distribution channels when possible. LLM verification: This skill is a legitimate troubleshooting guide for the 'uv' tool and its documented operations are consistent with that purpose. However the documentation repeatedly recommends high-risk install patterns (curl | sh to https://astral.sh/uv/install.sh), unpinned installs (pip install uv), and destructive shell commands (rm -rf ~/.cache/uv). Those patterns are supply‑chain and operational risks because they execute remote code and delete files without safe, pinned verification. There's no direct