@programinglive/dev-workflow-mcp-server@1.23.2
MCP server to enforce development workflow discipline
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe lifecycle hooks perform local workflow setup, and the flagged setup and process execution code is gated behind explicit commands. The reviewed source shows no attack behavior or unrelated data collection.
Decision evidence
public snapshot- The postinstall hook creates an initial workflow state file in the invoking project; it does not transmit project data.
- The prepare hook skips Husky setup when the package checkout has no .git directory.
- The setup-stack script only starts setup when run directly, and the server only starts when index.js is run directly.
- The postinstall hook creates a .state directory and workflow-state.json in the invoking project when that file is absent.
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.23.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.23.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.