registry / @programinglive/dev-workflow-mcp-server / 1.19.28
@programinglive/dev-workflow-mcp-server@1.19.28
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook writes a local initial state file, while the prepare hook skips outside a Git checkout. Runtime monitoring is disabled unless configured, and setup changes to OpenCode configuration require an explicit setup command.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install creates local workflow state; monitoring sends only when DEVWF_MONITOR_URL is configured; broader agent setup requires explicitly running the setup script.
Impact
No unauthorized data collection, credential theft, or concealed execution was identified. Configured monitoring can transmit project and task metadata to the endpoint the operator selects.
Mechanism
The install hook initializes .state/workflow-state.json. Optional monitoring posts workflow metadata to the configured endpoint; the mobile dashboard client reads from its configured or bundled monitor address.
AI rationale
The install hook writes a local initial state file, while the prepare hook skips outside a Git checkout. Runtime monitoring is disabled unless configured, and setup changes to OpenCode configuration require an explicit setup command.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
Network endpoints2
<DEVWF_MONITOR_URL>/api/session100.107.65.21:3100
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook creates an initial local workflow state file and skips this when installing inside node_modules.
- The prepare script skips Husky setup when the package directory is not a Git checkout.
- Monitor reporting is disabled unless DEVWF_MONITOR_URL is set; when enabled, it sends workflow metadata such as machine name, project path, task and plan after state saves.
- The broader OpenCode setup runs only when its setup script is invoked directly, corresponding to the package's explicit setup command.
- The mobile monitor client uses a configured URL or a fixed monitor address to retrieve dashboard data.
Evidence against
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.28.
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.28 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.