@programinglive/dev-workflow-mcp-server@1.19.27
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe lifecycle and setup behavior supports the package's workflow tooling: install initializes local state, while external agent configuration is handled by an explicit setup command. Runtime monitoring is disabled unless an endpoint is configured; no concealed collection or unrelated data transfer was identified.
Decision evidence
public snapshot- The postinstall hook initializes a project workflow state file and skips creation when that file already exists; it does not send data.
- Runtime monitoring sends only when DEVWF_MONITOR_URL is configured, and the snapshot fields support the package's workflow monitoring feature.
- OpenCode configuration and AGENTS.md setup runs through the separate setup command when directly invoked.
- The mobile app polls a monitor endpoint for session data; its URL can be overridden through app configuration.
- When monitoring is configured, snapshots include the machine name, local project path, task description, and plan.
- The postinstall hook writes a .state/workflow-state.json file under the invoking project directory.
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.27.
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.27 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.