T08 · Insecure Dependencies
- Location
README.md:20- Finding
Unpinned Third-Party CLI Is Downloaded and Executed During Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill content is coherent and privacy-aware, but its documentation includes an unpinned npx installer that can execute mutable third-party code during installation.
Use the OpenClaw install path where possible. If using the Skills Hub npx command, pin and verify the CLI version first, and do not run it from an elevated shell. Be mindful that real resumes can contain sensitive personal data even though the skill instructs the agent not to repeat contact details.
README.md:20Unpinned Third-Party CLI Is Downloaded and Executed During Installation
The natural-language content for the skill description, use cases, and verify prompt is written in Chinese, but the file does not state that the skill is China-specific or give users an option to choose another language. This can violate language/locale policy expectations because it effectively forces a specific language without user opt-in.
The marketplace file instructs users to run npx @skills-hub-ai/cli install resume-interview-generator-2 without pinning an exact package version. That creates a supply-chain risk: users may execute whatever version is current at install time, including a compromised or maliciously updated release. Because this is an installation command in user-facing documentation, the skill context makes the issue more dangerous than a passive reference.
The README instructs users to run npx @skills-hub-ai/cli install resume-interview-generator-2 without pinning an exact package version. This creates a supply-chain risk because a future compromised or maliciously updated package version could be fetched and executed implicitly on the user's system. The skill context increases concern because installation instructions are likely to be copied verbatim by users, making exploitation practical.
The file explicitly states "Default language: 中文", which imposes a language default in natural-language documentation. Under the policy, locale or language constraints should either offer user opt-in/choice or be clearly justified as region-specific; neither is present here.
The README instructs users to run an unpinned npx @skills-hub-ai/cli install ... command, which fetches and executes the latest published package at install time. If the upstream package is compromised, typo-squatted, or a malicious version is published, users could execute attacker-controlled code on their local machine during installation.
The instruction at L3 is written as a direct requirement in Chinese and does not offer any language or locale choice to the user. Under the policy, forcing a specific language without opt-in is a natural-language policy violation unless the locale restriction is clearly justified.
The title, summary, keywords, and user_needs are all written only in Chinese, which indicates a language-specific experience but provides no indication that the skill is China-region-specific or that users can choose another language. This creates a natural-language policy concern because the skill appears to enforce a specific locale without opt-in or justification.
The README explicitly states 'Default language: 中文', which imposes a locale/language default in natural-language documentation. Under the policy, forcing a specific language without offering a user choice or opt-in can be a language/locale policy violation.
The file specifies an output language choice but sets the default to Chinese, which imposes a locale preference unless the user notices and overrides it. Under the policy, language constraints should be opt-in or clearly justified; this default behavior is not justified as region-specific.
SQP-3 applies to all file types and covers language or locale policy violations. This markdown guidance forces a specific language for users/readers with no opt-in, alternative locale, or justification that the skill is region-specific.
The file title and introductory description are written entirely in Chinese, and the rest of the skill content continues in that language with no indication that users may choose another language. Under the policy rule for language/locale, this is a natural-language constraint that lacks user opt-in or justification as a region-specific tool.
No suspicious patterns detected.