registry / @programinglive/dev-workflow-mcp-server / 1.20.3
@programinglive/dev-workflow-mcp-server@1.20.3
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook creates a project-local workflow state file, while global OpenCode changes occur through the explicit setup command. Optional monitoring sends workflow metadata only when DEVWF_MONITOR_URL is configured; no malicious behavior was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The postinstall hook creates project workflow state; global agent setup and optional monitor reporting require configuration or an explicit setup command.
Impact
No malicious behavior identified. Configured monitor reporting includes project and task metadata.
Mechanism
Creates a project-local state file, configures OpenCode when setup is explicitly run, and sends workflow metadata only when DEVWF_MONITOR_URL is configured.
AI rationale
The install hook creates a project-local workflow state file, while global OpenCode changes occur through the explicit setup command. Optional monitoring sends workflow metadata only when DEVWF_MONITOR_URL is configured; no malicious behavior was identified.
Evidence
.state/workflow-state.json~/.config/opencode/opencode.jsonAGENTS.md
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Monitor reporting is disabled when DEVWF_MONITOR_URL is empty.
- When enabled, monitor snapshots contain workflow metadata such as project path, task description, phase, and plan.
- The global OpenCode setup runs through the explicit npm run setup command.
- The postinstall hook creates a workflow state file in the installer's project directory and skips creating it if it already exists.
Evidence against
- The monitor can send identifying project and task metadata when configured with a URL.
- The explicit setup command modifies global OpenCode configuration and may install dependencies.
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.3.
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.3 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.