@programinglive/dev-workflow-mcp-server@1.20.0
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThis is warning-level runtime telemetry: it is disabled unless a monitor URL is configured, but the transmitted snapshot includes identifying project and task details. No install-time exfiltration or fixed external collector was identified.
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 configured.
Impact
The endpoint receives machine and project details, task descriptions, plans, and session metadata.
Mechanism
The reporter posts a snapshot to the configured URL's /api/session endpoint.
AI rationale
This is warning-level runtime telemetry: it is disabled unless a monitor URL is configured, but the transmitted snapshot includes identifying project and task details. No install-time exfiltration or fixed external collector was identified.
Evidence
monitor.jsworkflow-state.js
Network endpoints1
User-configured DEVWF_MONITOR_URL host; no fixed host in source
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- When DEVWF_MONITOR_URL is set, the monitor sends a POST request to that configured endpoint.
- The snapshot includes machine and project identifiers, task description, workflow plan, and session metadata.
- Workflow state saves automatically invoke the monitor reporter.
- The postinstall script creates a local .state/workflow-state.json file under the invoking project directory.
Evidence against
- The monitor does not send when DEVWF_MONITOR_URL is empty; no fixed endpoint is defined in monitor.js.
- The install hook's observed behavior is local state-file setup, not network transmission.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
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 Limiteddb/adapters/sqlite.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.20.0.
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.20.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.