T08 · Insecure Dependencies
- Location
SKILL.md:69- Finding
Unpinned Third-Party Skill Installation and Execution
- Content
View full analysis
/scripts/render-elk.mjs diagram.json output.svg # Batch: all .json files in a folder → svg/ subfolder node /scripts/render-elk.mjs --dir # Batch + PNG (macOS only) node /scripts/render-elk.mjs --dir --png ``` Replace `` with the path to the installed diagrams skill directory. > **Note:** elkjs must be installed locally where you run the script. See the diagrams skill's SKILL.md for full setup. **Workflow for each diagram:** 1. Write the ELK JSON to a `.json` file in the research folder 2. Render: `node /scripts/render-elk.mjs diagram.json diagram.svg` 3. Embed in the markdown doc: `` 4. Keep both the `.json` (source of truth) and `.svg` (rendered) in the research folder ``` ### Technical Analysis The workflow directs the user or agent to install the third-party `diagrams` skill by a mutable package name and then execute its JavaScript renderer with Node.js. No immutable version, commit digest, integrity hash, trusted publisher identity, or mandatory source review is specified. The `diagrams` dependency is not included in the audited project, so its implementation and behavior could not be inspected. If the package source, publisher account, registry entry, or dependency-resolution process is compromised, the installed `render-elk.mjs` file could contain attacker-controlled code. Node.js executes that code with the permissions and environmental access of the invoking user or agent. ...[truncated 1727 chars]- Remediation
View remediation
