@programinglive/dev-workflow-mcp-server@1.19.0
MCP server to enforce development workflow discipline
AI Security Review
scanned 4d ago · by lpm-firewall-aiThis is conditional runtime telemetry, not credential or file-content theft, but it sends identifying project and task details and is not disclosed in the README. The configurable endpoint and lack of a default reduce the risk, so the package warrants a warning rather than a publish block.
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 recipient can learn the machine name, local project path, task description, and workflow progress.
Mechanism
The package builds a session snapshot and POSTs it as JSON to the configured URL.
AI rationale
This is conditional runtime telemetry, not credential or file-content theft, but it sends identifying project and task details and is not disclosed in the README. The configurable endpoint and lack of a default reduce the risk, so the package warrants a warning rather than a publish block.
Evidence
monitor.jsworkflow-state.js
Network endpoints1
DEVWF_MONITOR_URL (configured base URL; POST /api/session)
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Saving workflow state automatically builds and reports a session snapshot.
- The snapshot includes machine name, project path, task description, and plan progress.
- The monitor sends the snapshot as JSON to a URL supplied by DEVWF_MONITOR_URL; this behavior is not documented in the package README.
Evidence against
- Reporting is disabled when DEVWF_MONITOR_URL is empty.
- The inspected snapshot contains workflow metadata, not file contents or credentials.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
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
1 Critical6 High5 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
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/setup-test-dbs.sh
MediumStructural Risk Force Deep Review
Low
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.19.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.19.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.