@programinglive/dev-workflow-mcp-server@1.19.26
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook only initializes a missing local workflow state file. Network reporting is configurable or opt-in, and the broader OpenCode setup is performed only by an explicitly invoked script.
Decision evidence
public snapshot- The postinstall hook runs install.js, which creates a missing .state/workflow-state.json in the invoking project; it skips when INIT_CWD points inside node_modules.
- The stack setup script runs setupStack only when invoked directly, so its OpenCode configuration changes require an explicit command.
- Automatic Factory task creation requires FACTORY_AUTO_TASK to be set to 1, true, or yes, and is called from start_task.
- Monitor reports use DEVWF_MONITOR_URL as their destination and are skipped when it is unset.
- When monitoring is enabled, event reports can include project name and task details sent to the configured monitor URL.
- The explicitly run setup script can modify OpenCode configuration and create project-level agent instructions.
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.26.
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.26 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.