@programinglive/dev-workflow-mcp-server@1.13.9
MCP server to enforce development workflow discipline
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe automatic postinstall action creates an empty workflow state file consistent with the package’s stated purpose. Network installation and broader OpenCode or agent configuration changes are tied to explicit setup scripts; no malicious data flow or concealed automatic behavior was identified.
Decision evidence
public snapshot- The package describes itself as an MCP server for development workflow discipline.
- The postinstall hook runs install.js, which initializes an empty .state/workflow-state.json under the invoking project directory.
- The package starts its MCP server only when index.js is run directly.
- The broader OpenCode configuration and AGENTS.md setup is performed by the explicitly invoked setup command.
- The bootstrap shell helper downloads the RTK installer from its project’s official GitHub host only when the helper is run and RTK is absent.
- Postinstall does create a file in the invoking project automatically.
- The optional setup command modifies OpenCode configuration and may create project-level AGENTS.md instructions.
Source & flagged code
9 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.13.9.
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.13.9 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.