@programinglive/dev-workflow-mcp-server@1.19.29
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe lifecycle side effects initialize state for the package’s stated workflow purpose, and the Husky helper skips registry installs. Network reporting is limited to metadata sent to an operator-configured monitor; the agent configuration changes require explicitly running the setup command.
Decision evidence
public snapshot- The manifest’s lifecycle hooks run a workflow-state initializer and a Husky helper.
- The postinstall initializer creates `.state/workflow-state.json` in the installing project and leaves an existing state file intact; this matches the package’s workflow-state purpose.
- The prepare helper skips Husky setup when the package is not in a Git checkout.
- OpenCode configuration and AGENTS.md setup runs only when the separate setup script is directly invoked.
- Monitor reporting requires a configured `DEVWF_MONITOR_URL`; its documented payload is workflow metadata, not file contents.
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.19.29.
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.19.29 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.