registry / @programinglive/dev-workflow-mcp-server / 1.20.1
@programinglive/dev-workflow-mcp-server@1.20.1
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hooks initialize workflow state and skip Husky setup outside a Git checkout. The setup utility is user-run, and monitoring has no default endpoint; its configured endpoint receives workflow metadata.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installation initializes workflow state; stack setup requires a direct user invocation; monitoring requires a configured URL.
Impact
No malicious behavior identified. A configured monitor receives workflow metadata such as task details and project path.
Mechanism
The install hook writes project workflow state. The optional monitor posts metadata to DEVWF_MONITOR_URL.
AI rationale
The install hooks initialize workflow state and skip Husky setup outside a Git checkout. The setup utility is user-run, and monitoring has no default endpoint; its configured endpoint receives workflow metadata.
Evidence
<projectRoot>/.state/workflow-state.json<configDir>/opencode.json<targetProjectRoot>/AGENTS.md
Network endpoints2
DEVWF_MONITOR_URL (user-configured): /api/sessionDEVWF_MONITOR_URL (user-configured): /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 creates the package's workflow state file under the invoking project directory.
- The prepare hook skips Husky setup when the package is not in a Git checkout.
- The broader agent-stack setup runs only when its script is invoked directly; it preserves an existing AGENTS.md.
- Monitor reporting is disabled unless DEVWF_MONITOR_URL is set, and sends workflow metadata to that configured URL.
Evidence against
- The install hook writes into the consumer project, but the file is workflow state for the package's stated purpose.
- The optional monitor payload includes the project path, task description, and machine name, so users should configure its URL deliberately.
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.1.
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.1 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.