T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Third-Party Secret-Management Dependency
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherently about local secrets management, but it needs Review because it recommends risky secret exposure patterns and an unpinned third-party CLI that would handle sensitive credentials.
Review this before installing. Only use a pinned, trusted version of the `keys` CLI, avoid `eval $(keys expose)`, avoid printing secrets to terminal output, protect generated .env files with file permissions and .gitignore, and sync secrets only between trusted machines on trusted networks.
SKILL.md:14Unpinned Third-Party Secret-Management Dependency
SKILL.md:207Shell Command Injection Through Evaluation of Exported Secrets
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
name: keys-manager
description: Manage API keys locally from the terminal using the `keys` CLI. Use when users want to store, retrieve, search, import, export, or organize API keys and secrets. Handles .env file operations, profile-based key isolation, and secure key management workflows.
metadata:
openclaw:
requires:
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
name: keys-manager
description: Manage API keys locally from the terminal using the `keys` CLI. Use when users want to store, retrieve, search, import, export, or organize API keys and secrets. Handles .env file operations, profile-based key isolation, and secure key management workflows.
metadata:
openclaw:
requires:
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
name: keys-manager
description: Manage API keys locally from the terminal using the `keys` CLI. Use when users want to store, retrieve, search, import, export, or organize API keys and secrets. Handles .env file operations, profile-based key isolation, and secure key management workflows.
metadata:
openclaw:
requires:
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
name: keys-manager
description: Manage API keys locally from the terminal using the `keys` CLI. Use when users want to store, retrieve, search, import, export, or organize API keys and secrets. Handles .env file operations, profile-based key isolation, and secure key management workflows.
metadata:
openclaw:
requires:
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
name: keys-manager
description: Manage API keys locally from the terminal using the `keys` CLI. Use when users want to store, retrieve, search, import, export, or organize API keys and secrets. Handles .env file operations, profile-based key isolation, and secure key management workflows.
metadata:
openclaw:
requires:
The skill instructs users to export secrets into .env files but does not warn that .env stores credentials in plaintext on disk, where they may be committed to source control, read by other local users, or captured by backups. Because this skill is specifically about managing secrets, omission of disk-handling warnings materially increases the chance of credential exposure.
The skill recommends keys inject, keys expose, and command substitution patterns that place secrets directly into shell commands or stdout without warning that credentials may leak via shell history, terminal logs, process inspection, CI logs, scrollback buffers, or command tracing. In a secrets-management skill, this is especially risky because the documented usage normalizes unsafe secret exposure paths.
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
The peer-to-peer sync feature transfers secrets across the network, and while the documentation mentions encryption, it does not warn users about trust boundaries, peer verification, local-network exposure, or the sensitivity of moving credentials between hosts. Users may incorrectly assume this is risk-free and sync secrets to less-trusted or compromised machines.
No suspicious patterns detected.