@programinglive/dev-workflow-mcp-server@1.13.2
MCP server to enforce development workflow discipline
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe lifecycle scripts perform package-related local setup: initializing workflow state and conditionally installing Husky hooks. The broader OpenCode and agent configuration setup is a separate explicit command; I found no malicious collection or transmission behavior.
Decision evidence
public snapshot- The package is an MCP server for development workflow tracking; its manifest maps `postinstall` to `install.js` and `setup` to a separate command.
- The postinstall uses `INIT_CWD` and creates `.state/workflow-state.json` only when it is absent; it skips when the path is inside `node_modules`.
- The `prepare` script skips outside a Git checkout and otherwise invokes Husky to install Git hooks.
- The OpenCode configuration setup is available through `npm run setup` and runs only when `setup-stack.js` is invoked directly.
- The MCP server starts only when `index.js` is run directly, not when it is imported.
- The postinstall automatically writes a workflow state file into the invoking project when that file does not exist.
- The prepare lifecycle may install Git hooks when the package itself is in a Git checkout.
- The explicit setup command can change OpenCode configuration and install the Superpowers plugin.
Source & flagged code
9 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.13.2.
See all versions of @programinglive/dev-workflow-mcp-server for other recorded verdicts.
- Review the evidence and your use of @programinglive/dev-workflow-mcp-server@1.13.2 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.