Why this verdict
- suspicious: finding skill:skills/favicons:skills/favicons/references/rule.md:741:EXEC
Security findings 1
Code execution
highContextual risklow confidenceThe skill's reference documentation instructs running 'node scripts/generate-favicons.js src/images/logo.png', and since that script is not shipped in the repository, an agent following the instruction executes whatever occupies that path at runtime.
node scripts/generate-favicons.js src/images/logo.png
vector:instruction
Counter-argument considered
The follow-up confirms the referenced script is unshipped, so the command the reference documentation wires into the project build would make an agent execute whatever occupies that path at runtime; the documented generator source is benign, but documentation never neutralizes a run-unshipped-content instruction, and executing unspecified code is not the declared markup-validation capability nor any other carve-out.
Open questions 3
What the analysis could not settle from the code alone.
[file request skills/favicons/scripts/generate-favicons.js] The package.json example in references/rule.md also invokes 'node scripts/generate-favicons.js src/images/logo.png'. Does this script ship in the artifact, and if so, does it fetch remote content, read credentials, write outside the project, or execute anything beyond generating favicon images from the given source image?
Code execution
[file request skills/favicons/scripts/validate-favicons.js] The package.json example in references/rule.md defines a script 'node scripts/validate-favicons.js'. Does this artifact ship that script, and if so, what does it do beyond favicon validation?
Code execution
[file request skills/favicons/scripts/validate-favicons.js] The package.json example in the reference doc invokes 'node scripts/validate-favicons.js'. Does this script exist in the artifact, and if so, does it read credentials, fetch remote content, write outside the project, or execute anything beyond checking favicon files?
Code execution
Coverage gaps 4
Parts of the artifact the static analysis could not fully examine.
context:unanalyzable_binary binary content is only byte-scanned
apps/web/public/projects/indie-dev-toolkit/indie-dev-toolkit.mp4
context:unanalyzable_binary binary content is only byte-scanned
docs/audits/2026-10-04-mcp-validation/assets/checklist-interaction.webm
context:unanalyzable_binary binary content is only byte-scanned
docs/audits/2026-10-04-mcp-validation/assets/mcp-tab-interaction.webm
context:manifest_unparseable yaml: YAML node count exceeds 20000
pnpm-lock.yaml
