@programinglive/dev-workflow-mcp-server@1.18.1
MCP server to enforce development workflow discipline
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe lifecycle hooks do not contact a collector or access credentials: postinstall only creates an absent workflow-state file, and prepare skips Husky setup outside a Git checkout. Configuration changes and the RTK download belong to separately invoked setup scripts and match the package's stated purpose.
Decision evidence
public snapshot- The manifest declares prepare and postinstall hooks.
- postinstall skips execution from inside node_modules and creates an initial .state/workflow-state.json only when that file is absent.
- The prepare hook skips Husky setup when the package directory has no .git checkout.
- OpenCode configuration and AGENTS.md changes are performed by the separate setup script when directly run.
- The Unix bootstrap downloads RTK's installer from its named GitHub repository only when the user invokes the bootstrap and RTK is missing.
- postinstall does write workflow state into the directory where npm install was invoked.
- The explicit setup command can modify OpenCode configuration and add an AGENTS.md file to the target project.
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.18.1.
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.18.1 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.