@programinglive/dev-workflow-mcp-server@1.13.4
MCP server to enforce development workflow discipline
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe lifecycle hooks perform limited setup consistent with the package’s workflow tooling purpose. The broader OpenCode and agent configuration changes are behind an explicit setup command, and the reviewed source shows no malicious collection or transmission of user data.
Decision evidence
public snapshot- The postinstall hook initializes workflow state in the invoking project and skips when the state file already exists.
- The prepare hook skips Husky setup when the package is not in a Git checkout.
- OpenCode configuration and agent setup run through the explicit `npm run setup` command, whose script runs only when directly invoked.
- The main entry starts the MCP server only when directly run; importing it does not start the server.
- The install hooks write a workflow state file and may invoke Husky in a Git checkout.
- The explicit setup command edits OpenCode configuration and may create an AGENTS.md file.
- The setup scripts can install dependencies and RTK from its official GitHub release infrastructure.
Source & flagged code
10 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.4.
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.4 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.