T08 · Insecure Dependencies
- Location
SKILL.md:28- Finding
Unpinned Executable Third-Party Dependencies
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a real HTML-conversion skill, but it expands into unpinned and dynamically loaded code, third-party scripts, uploads, and publishing without enough guardrails.
Install only if you are comfortable reviewing generated HTML before sharing it, using trusted/pinned dependencies, and avoiding private documents or local images unless you control the upload and hosting destination. Treat inherited HTML as untrusted unless it has been sanitized, and prefer offline or bundled chart assets for sensitive reports.
SKILL.md:28Unpinned Executable Third-Party Dependencies
assets/chart_helper.js:21Runtime Retrieval and Execution of Integrity-Free CDN JavaScript
scripts/inherit_layout.py:139Inherited HTML Preserves Untrusted Active Content
If the actual implementation only injects assets into existing HTML while the skill advertises full conversion, themeing, title/favicon changes, publishing, and layout inheritance, then the user is misled about what data transformations and network actions occur. Misrepresentation is security-relevant here because it can conceal external resource loading and publication behavior that may expose sensitive document content.
If the actual implementation only injects assets into existing HTML while the skill advertises full conversion, themeing, title/favicon changes, publishing, and layout inheritance, then the user is misled about what data transformations and network actions occur. Misrepresentation is security-relevant here because it can conceal external resource loading and publication behavior that may expose sensitive document content.
If the actual implementation only injects assets into existing HTML while the skill advertises full conversion, themeing, title/favicon changes, publishing, and layout inheritance, then the user is misled about what data transformations and network actions occur. Misrepresentation is security-relevant here because it can conceal external resource loading and publication behavior that may expose sensitive document content.
If the actual implementation only injects assets into existing HTML while the skill advertises full conversion, themeing, title/favicon changes, publishing, and layout inheritance, then the user is misled about what data transformations and network actions occur. Misrepresentation is security-relevant here because it can conceal external resource loading and publication behavior that may expose sensitive document content.
If the actual implementation only injects assets into existing HTML while the skill advertises full conversion, themeing, title/favicon changes, publishing, and layout inheritance, then the user is misled about what data transformations and network actions occur. Misrepresentation is security-relevant here because it can conceal external resource loading and publication behavior that may expose sensitive document content.
If the actual implementation only injects assets into existing HTML while the skill advertises full conversion, themeing, title/favicon changes, publishing, and layout inheritance, then the user is misled about what data transformations and network actions occur. Misrepresentation is security-relevant here because it can conceal external resource loading and publication behavior that may expose sensitive document content.
If the actual implementation only injects assets into existing HTML while the skill advertises full conversion, themeing, title/favicon changes, publishing, and layout inheritance, then the user is misled about what data transformations and network actions occur. Misrepresentation is security-relevant here because it can conceal external resource loading and publication behavior that may expose sensitive document content.
The module dynamically imports and executes Python code from an environment-controlled file path (EASY_HTML_CSS_ENGINE) and from attacker-influenced local directories such as the current working directory. That means anyone who can influence the runtime environment or place files in searched locations can achieve arbitrary code execution when the skill loads the CSS engine. In a content-conversion skill, treating a theme engine as executable Python rather than trusted packaged data makes this especially dangerous because the feature can be triggered during normal operation.
The README explicitly documents a publish step for generated HTML but does not warn users that the output may contain sensitive source content and, once published, can become publicly accessible. In this skill's context, inputs may come from reports, spreadsheets, Word documents, or images, so users could unintentionally expose confidential business or personal data by following the documented workflow.
The skill describes capabilities that involve environment access, file writes, and network use, but it does not declare any explicit tool scope or permission boundaries. That creates ambiguity for the orchestrator and reviewers, increasing the chance the skill can access or invoke more capability than users reasonably expect, especially around publishing and external asset loading.
The top-level description advertises publishing as a live page but does not clearly warn that publication can make the user's content publicly accessible. This is dangerous because users may provide internal documents, tables, or converted office files expecting local formatting, then inadvertently expose sensitive information when a later publish step is invoked.
The trigger phrases are broad enough to match routine requests like 'make this pretty' or 'turn this into a web page,' which can cause the skill to activate on unrelated or sensitive content without clear user intent. In this skill's context, accidental activation is more dangerous because the workflow includes writing files, optional publishing, and external asset loading, increasing the chance of unintended data exposure.
The natural-language guidance and user-visible fallback text are written only in Chinese, and the file does not indicate that the skill is region-specific or that users may choose another language. Under the policy, forcing a specific language without opt-in is a locale/language policy violation.
This helper dynamically loads executable JavaScript from public CDNs at runtime, which introduces a supply-chain and privacy risk beyond a purely local HTML conversion feature. If a CDN, mirror, or configured override source is compromised, blocked, or replaced, the generated page will execute untrusted code in the viewer's browser.
The fallback message shown to end users is hardcoded as Chinese text only, with no mechanism for locale selection or opt-in. This can force a specific language experience on users outside that locale and violates the language-choice policy unless the skill is explicitly documented as region-specific.
This markdown file contains user-facing instructional content exclusively in Chinese, and there is no indication that the skill is region-specific or that users can opt into another language. That creates a natural-language policy concern under the language/locale rule because it implicitly forces a specific language experience.
Line L43 states '中文优先', directing labels and explanatory text to be in Chinese by default. This is a natural-language locale policy constraint, and the file does not indicate that users may choose another language or opt in to the Chinese-only preference.
The documentation explicitly instructs the agent to upload local images to arbitrary external image hosting or object storage in order to preserve them in generated HTML. That expands the skill from local content transformation into network publication/exfiltration behavior, which can leak sensitive local files or user-provided documents to third parties without strong trust, consent, destination restrictions, or data-handling controls.
This markdown file is written as a skill manual entirely in Chinese, and it does not indicate that the language is optional, configurable, or limited to a justified region-specific audience. Under the natural-language policy rules, forcing a specific language without user opt-in is a locale-policy concern.
The title and all operational instructions are written as a mandatory workflow in Chinese, and the file does not indicate that users may choose another language or that the skill is region-specific. This can violate a language/locale policy when a skill implicitly forces one language without user opt-in.
This code file contains natural-language instructions and CLI/help text exclusively in Chinese, including the module docstring and usage examples. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly justified, which is not present here.
This code file contains natural-language documentation and CLI/log strings entirely in Chinese, including the module docstring and runtime messages. The file does not indicate that the tool is region-specific or provide any user language selection, which creates a language/locale policy issue under the stated rule.
A substantial portion of the skill's instructional content is presented only in Chinese, with no indication that the user can choose another language or locale. This can amount to a language/locale policy issue when the skill experience implicitly forces one language without user opt-in.
The file header states that when Chart.js fails, the canvas area will show a failure message plus a fallback original data table. In actual code, both degrade() and degradeAll() replace chart canvases only with a text message and never render any tabular representation of the original data.
This code dynamically fetches and executes a third-party script from multiple public CDN endpoints, which is a network operation that can transmit user/system metadata such as IP address and request headers. The file contains no confirmation, user-visible log, or warning comment informing users that external resources will be contacted at runtime.