registry / @programinglive/dev-workflow-mcp-server / 1.20.4
@programinglive/dev-workflow-mcp-server@1.20.4
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook creates project-local workflow state, and optional monitoring is gated by an operator-provided URL. I found no credential collection, unrelated host contact, or concealed harmful action.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Install initializes project-local workflow state; monitoring depends on DEVWF_MONITOR_URL; broader agent setup runs through npm run setup.
Impact
No malicious impact identified. If configured, monitoring can receive project and task metadata at the operator-selected endpoint.
Mechanism
The install hook writes workflow state locally. Optional monitoring sends workflow snapshots to the configured endpoint; agent setup is a separate command.
AI rationale
The install hook creates project-local workflow state, and optional monitoring is gated by an operator-provided URL. I found no credential collection, unrelated host contact, or concealed harmful action.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
Network endpoints2
$DEVWF_MONITOR_URL/api/session$DEVWF_MONITOR_URL/api/event
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook uses INIT_CWD and creates a workflow state JSON file in the project; the inspected install code showed no network activity.
- Monitor reporting uses DEVWF_MONITOR_URL, which is empty unless configured, and posts workflow snapshots to that configured endpoint.
- The package exposes agent setup as a separate npm run setup command; setupStack calls the routine that creates AGENTS.md.
Evidence against
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 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.20.4.
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.4 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.