@programinglive/dev-workflow-mcp-server@1.19.21
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package sends identifying project and task metadata automatically on workflow saves when monitoring is enabled, while the README does not disclose this telemetry. The configurable endpoint and disabled-by-default behavior make this a warning-level telemetry issue rather than evidence of malicious exfiltration.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A workflow state save while DEVWF_MONITOR_URL is set.
Impact
The configured monitor receives potentially identifying project details and task content. No telemetry consent prompt or disclosure was found in the inspected README.
Mechanism
The package posts a session snapshot to the configured URL's /api/session endpoint. The snapshot includes project path, task description, plan, machine name, and session title.
AI rationale
The package sends identifying project and task metadata automatically on workflow saves when monitoring is enabled, while the README does not disclose this telemetry. The configurable endpoint and disabled-by-default behavior make this a warning-level telemetry issue rather than evidence of malicious exfiltration.
Evidence
monitor.jsworkflow-state.js${INIT_CWD}/.state/workflow-state.json
Network endpoints1
${DEVWF_MONITOR_URL}/api/session
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- When DEVWF_MONITOR_URL is set, saving workflow state automatically reports a session snapshot.
- The snapshot includes the project path, task description, plan, machine name, and session title.
- The monitor endpoint is configurable and reporting is disabled when DEVWF_MONITOR_URL is empty.
- The postinstall hook creates a workflow state file under the installer's project directory.
Evidence against
- No fixed external monitor host is embedded; the endpoint comes from DEVWF_MONITOR_URL.
- Monitor reporting is disabled by default.
- The package's documented purpose includes workflow state tracking, and the install hook only initializes that state when absent.
- Agent configuration setup runs only when scripts/setup-stack.js is invoked directly.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
11 flaggedpackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgexec.jsView file
1import { exec as execCallback, execFile as execFileCallback } from "child_process";
L2: import { existsSync } from "fs";
High
Findings
1 Critical6 High6 Medium6 Low
CriticalPrevious Version Dangerous Deltaworkflow-state.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processexec.js
HighShellscripts/install-husky.js
HighSandbox Evasion Gated Capabilityscripts/setup-stack.js
HighRuntime Package Installscripts/setup-stack.js
HighSemantic Analysis Limitedexec.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiresecurity/log-bridge.cjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/setup-test-dbs.sh
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.19.21.
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.21 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.