@programinglive/dev-workflow-mcp-server@1.14.2
MCP server to enforce development workflow discipline
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe automatic lifecycle scripts perform package-related initialization and Git hook setup without an identified data collection or unrelated network action. The broader OpenCode configuration and plugin setup is an explicit, purpose-aligned command.
Decision evidence
public snapshot- The postinstall initializer creates a missing workflow state file in the invoking project; it contains workflow fields, not collected host or credential data.
- The prepare hook skips outside a Git checkout and otherwise invokes Husky to install hooks.
- The main entry starts the server or CLI only when run directly; importing it does not start them.
- The optional setup command edits OpenCode configuration and registers the workflow stack, matching the package's setup purpose.
- The package declares automatic prepare and postinstall lifecycle hooks.
- The optional setup command changes OpenCode configuration and can install the Superpowers plugin; its bootstrap script can download and run RTK's installer.
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.14.2.
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.14.2 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.