deskclaw-security-vuln-check

Detect residual litellm installations in DeskClaw runtime environments and Python interpreters.

Updated Mar 3, 2026

Search Tags:#security #vulnerability #python #audit #dependency #litellm #deskclaw

Ready to run

npx skills add https://github.com/zinohome/zinoClaw --skill deskclaw-security-vuln-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deskclaw-security-vuln-check
Source: https://github.com/zinohome/zinoClaw/tree/main/docker-customize/deskclaw-resources/skills/deskclaw-security-vuln-check
Command: npx skills add https://github.com/zinohome/zinoClaw --skill deskclaw-security-vuln-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps identify lingering litellm installations in DeskClaw runtime environments and Python interpreters, reducing uncertainty during security audits and upgrades.

Core Features & Use Cases

Gateway Environment Auditing: Checks the DeskClaw gateway-venv for installed litellm packages using package metadata, import detection, and filesystem inspection.
Python Path Scanning: Reviews distinct Python interpreters available through PATH and reports detected litellm versions, including flagged advisory versions.
Use Case: After upgrading DeskClaw, use this Skill to verify that old dependency remnants are removed and understand whether any remaining installations require attention.

Quick Start

Run the DeskClaw security vulnerability check skill to audit gateway-venv and available Python interpreters for litellm remnants.

Frequently Asked Questions about deskclaw-security-vuln-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check for vulnerable litellm remnants in a Python environment?▼

You can scan multiple Python interpreters by reviewing distinct executables available through PATH. The audit checks each cross-platform interpreter location for litellm package presence, version details, and import availability to identify residual installations.

What is the best way to verify dependency hygiene after upgrading DeskClaw?▼

Verifying dependency hygiene after a DeskClaw upgrade involves running an environment validation script to ensure old dependency remnants are removed. It checks package metadata and filesystem traces to confirm whether remaining installations require further attention.

Does the litellm vulnerability audit work across different Python interpreters?▼

Yes, the litellm vulnerability audit works across different Python interpreters by scanning distinct executables found in PATH. It reports detected litellm versions and cross-platform interpreter locations to support comprehensive security auditing workflows.

How do I detect lingering litellm installations in a gateway-venv?▼

Detect lingering litellm installations in a gateway-venv by inspecting package metadata, testing import availability, and scanning the filesystem for residual traces. This identifies leftover components and flags specific advisory versions that require removal.