@programinglive/dev-workflow-mcp-server
MCP server to enforce development workflow discipline
This report shows the evidence for @programinglive/dev-workflow-mcp-server@1.24.0. 0 of 64 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe automatic install behavior is limited to creating an initial local workflow state file, with no observed network contact, credential access, or unrelated action. The Husky hook skips outside a Git checkout, and the broader agent setup is gated behind an explicit command.
Decision evidence
public snapshot- The postinstall hook runs install.js, which initializes a workflow state file in the npm caller’s project and skips when installed inside node_modules.
- The inspected install.js only creates the initial .state/workflow-state.json when it does not already exist; it contains no network or credential collection behavior.
- The prepare script skips Husky setup when the package is not in a Git checkout.
- The added project search code requires a project root that is the Git repository root and filters sensitive paths.
Source & flagged code
11 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.24.0.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @programinglive/dev-workflow-mcp-server@1.24.0 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.