registry / @programinglive/dev-workflow-mcp-server / 1.19.30
@programinglive/dev-workflow-mcp-server@1.19.30
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook only initializes local workflow state, while broader agent setup requires an explicit command and monitoring is disabled unless configured. The reviewed behavior matches the package’s stated workflow-management purpose.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install creates local workflow state; broader OpenCode setup requires an explicit setup command. Monitoring requires DEVWF_MONITOR_URL.
Impact
No unauthorized data collection, credential transfer, or unrelated execution was identified.
Mechanism
The postinstall hook initializes a project-local state file. The explicit setup script configures OpenCode and may add AGENTS.md; configured monitoring sends workflow metadata to the supplied URL.
AI rationale
The install hook only initializes local workflow state, while broader agent setup requires an explicit command and monitoring is disabled unless configured. The reviewed behavior matches the package’s stated workflow-management purpose.
Evidence
.state/workflow-state.jsonAGENTS.mdopencode.json
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Package metadata identifies an MCP workflow server and points its main and bin entries to index.js.
- The postinstall hook creates a project-local .state/workflow-state.json file only if it is absent; it contains no network send.
- OpenCode and AGENTS.md setup changes are made by setup-stack.js only when that script is run directly.
- Runtime monitoring is disabled when DEVWF_MONITOR_URL is unset; configured reports send workflow metadata.
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.30.
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.30 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.