@programinglive/dev-workflow-mcp-server@1.19.24
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hooks perform package-related initialization and skip Husky setup outside a Git checkout. Runtime monitoring is off unless configured, and the reviewed startup path does not reveal automatic credential collection or unrelated network activity.
Decision evidence
public snapshot- The postinstall hook creates a workflow state file under the install project and skips creation when running inside node_modules.
- The prepare hook skips Husky setup outside a Git checkout; inside one, it runs the project’s Husky binary.
- Monitor reporting is disabled unless DEVWF_MONITOR_URL is set, and its payload contains workflow metadata rather than file contents.
- The setup-stack configuration changes run only when that script is invoked directly.
- The update-check script says it does not check the network automatically during MCP operation.
- When enabled, monitor reporting can send the machine name, project path, task description, and workflow plan to the configured URL.
- The explicit setup command can install dependencies and modify OpenCode configuration and AGENTS.md.
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.24.
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.24 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.