@programinglive/dev-workflow-mcp-server@1.23.3
MCP server to enforce development workflow discipline
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe install hook creates only the package’s workflow state file, while the Husky hook is limited to Git checkouts. Network reporting is configured by the user, automatic Factory task creation is opt-in, and broader OpenCode setup is explicitly invoked.
Decision evidence
public snapshot- The manifest’s postinstall initializes workflow state; prepare runs a Husky setup script.
- Postinstall creates `.state/workflow-state.json` in the invoking project and skips creation if it already exists.
- The prepare script skips Husky setup when the package directory is not a Git checkout.
- Monitor reports use `DEVWF_MONITOR_URL`; the source says the default is disabled and reports workflow metadata, not file contents.
- Automatic Factory task creation requires `FACTORY_AUTO_TASK=1` and configured Factory credentials.
- OpenCode setup and its configuration writes run through the explicit `setup` script, not automatically on import.
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.3.
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.3 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.