T08 · Insecure Dependencies
- Location
SKILL.md:162- Finding
Unpinned third-party packages are installed and executed
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a real Workflow Weaver integration, but its setup can expose long-lived credentials and runs mutable npm packages, so it should be reviewed before installation.
Install only if you trust the Workflow Weaver npm packages and service. Prefer pinned package versions, avoid `npx @latest`, do not print refresh tokens into an agent or terminal transcript, and avoid putting real tokens in project-local MCP config files. Review any source material before generating public share links, and rotate the Workflow Weaver token if it was exposed in logs or committed files.
SKILL.md:162Unpinned third-party packages are installed and executed
SKILL.md:50Authentication refresh token is printed to standard output
SKILL.md:176Long-lived credentials are embedded in plaintext MCP configuration files
The supplied code does not implement API documentation generation, diagram creation, workflow rendering, or export functionality. Instead, it is an operational test script for the Workflow Weaver CLI/MCP environment. Its primary purpose is validating installation and runtime behavior, especially around authentication, billing, and MCP protocol responses. These are materially different capabilities from the declared end-user documentation/diagram generation purpose, so this is a clear description-to-behavior mismatch.
The description says to use the skill when asked to 'create API docs, generate diagrams, build process guides, or turn code into visual workflows,' which are broad natural-language requests without clear boundaries or exclusions. In a manifest/markdown context, this can cause unintended activation for many ordinary user requests that may not specifically require this skill.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
| No hardcoded credentials | Never embed tokens, passwords, or keys in scripts, logs, or skill files |
| Refresh token via env var only | `WORKFLOW_WEAVER_REFRESH_TOKEN` — never interpolate into log lines or `echo` |
| Supabase credentials via env var only | `WORKFLOW_WEAVER_SUPABASE_URL` and `WORKFLOW_WEAVER_SUPABASE_KEY` — never in scripts |
| Config file path | `~/.workflow-weaver/config.json` (chmod 600) — document but never read directly in automation scripts; one-time setup extraction is acceptable |
| Stripe/billing URLs | Present to the user to open in a browser — never open programmatically |
| Smoke placeholder | Use clearly-named placeholders like `smoke-test-invalid-token`, never real-looking values |
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
"WORKFLOW_WEAVER_SUPABASE_KEY": "***"
},
"disabled": false,
"autoApprove": []
}
}
}
The skill documents creation of public share links but does not prominently warn that these links may expose project contents to anyone with the URL. In an agent context, users may not realize generated workflows or imported API sources could contain proprietary architecture, internal endpoints, or sensitive documentation.
No suspicious patterns detected.