@programinglive/dev-workflow-mcp-server@1.19.12
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has an optional monitor reporting path, but it sends identifying project and task metadata when enabled by environment configuration. Because this runtime reporting is not documented for users, classify it as suspicious telemetry rather than a block-level attack.
Static reason
One or more suspicious static signals were detected.
Trigger
A nonempty DEVWF_MONITOR_URL, followed by a workflow state save or reported event.
Impact
The monitor may receive the machine name, project path, task and plan text, and workflow activity.
Mechanism
The package POSTs snapshots to /api/session and events to /api/event at the configured base URL.
AI rationale
The package has an optional monitor reporting path, but it sends identifying project and task metadata when enabled by environment configuration. Because this runtime reporting is not documented for users, classify it as suspicious telemetry rather than a block-level attack.
Evidence
monitor.jsworkflow-state.jstools/handler-modules/commit-handlers.jstools/handler-modules/workflow-handlers.js
Network endpoints2
DEVWF_MONITOR_URL + /api/sessionDEVWF_MONITOR_URL + /api/event
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, the package sends session snapshots to that configured endpoint.
- Snapshots include the machine name, project path, task description, task type, phase, and plan.
- Workflow state saves trigger snapshot reporting; event reports can also include task text and details.
Evidence against
- Reporting is disabled when DEVWF_MONITOR_URL is empty, and no fixed remote host is present in this flow.
- The reported data is workflow metadata; the source says it does not send file contents.
- The separate agent setup script runs only when explicitly invoked.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
10 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
6 High6 Medium6 Low
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
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.19.12.
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.12 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.