T08 · Insecure Dependencies
- Location
SKILL.md:29- Finding
Mutable Third-Party Dependencies Are Installed Without Version or Integrity Pinning
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The SEO workflow is coherent, but its setup uses unpinned remote installers and updates all installed skills, which is broader than this skill needs.
Install only in an isolated environment, prefer pinned versions of the ClawHub CLI and dependencies, avoid `update --all`, expose only the API keys needed for the selected run, and do not submit confidential drafts or local files unless you are comfortable sending them to the named external providers.
SKILL.md:29Mutable Third-Party Dependencies Are Installed Without Version or Integrity Pinning
SKILL.md:34Global Update Command Modifies Unrelated Installed Skills
SKILL.md:7Over-Broad Credential Declaration and Insufficient Consent Controls for External Data Transmission
The skill instructs users to execute npx -y clawhub@latest install ..., which pulls and runs the latest package version at execution time rather than a pinned, reviewed release. This creates a supply-chain risk: if the upstream package or dependency chain is compromised, users may execute attacker-controlled code locally.
This line again directs execution of npx -y clawhub@latest, causing remote package resolution and code execution from an unpinned version. Because this is an orchestration skill that requires multiple local tools and credentials, compromise of the installer path could lead to arbitrary code execution and theft of API keys from the user's environment.
Using npx -y clawhub@latest install api-gateway executes whatever package version is current at the time, exposing users to package takeover or malicious update scenarios. The danger is amplified here because the installed components are intended to interact with external services and sensitive environment variables.
This installation instruction repeats the same unpinned npx pattern, allowing arbitrary newly published code to be executed on the user's machine. In the context of a skill that depends on API-backed tooling, a compromised installer could exfiltrate credentials or alter downstream tool behavior.
npx -y clawhub@latest update --all is especially risky because it can update multiple components in one step to unreviewed versions. This broadens the supply-chain exposure and can silently introduce malicious or breaking changes across the installed toolchain.
Even the verification step uses npx -y clawhub@latest list, which still requires resolving and running the latest remote package. Although lower risk than install/update actions, it remains an unnecessary code-execution path that could be abused if the package is compromised.
The skill references uvx markitdown without a pinned version, which similarly resolves and executes a package/tool dynamically. While this may be operationally convenient, it introduces the same class of supply-chain risk if the package or one of its dependencies is compromised.
The reference to uvx markitdown is unpinned, so executions may resolve to whatever package version is current at runtime rather than a reviewed version. That creates a supply-chain risk: future upstream changes, compromise of the package, or breaking behavior could alter file-conversion behavior in a skill that processes untrusted content, increasing the chance of malicious parsing effects or unexpected code execution paths.
No suspicious patterns detected.