registry / @programinglive/dev-workflow-mcp-server / 1.20.2
@programinglive/dev-workflow-mcp-server@1.20.2
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe lifecycle scripts perform project workflow-state initialization and skip Husky setup outside a Git checkout. Network reporting is opt-in through DEVWF_MONITOR_URL, and the broader agent configuration setup runs only when explicitly invoked.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm postinstall creates workflow state; optional monitoring requires a configured URL; stack setup requires a direct user invocation.
Impact
No malicious impact identified. Automatic installation creates project-local workflow state; configured reporting shares workflow metadata with the chosen endpoint.
Mechanism
The install hook initializes a workflow-state file. Optional reporting sends workflow metadata to DEVWF_MONITOR_URL. Explicit setup configures the OpenCode stack.
AI rationale
The lifecycle scripts perform project workflow-state initialization and skip Husky setup outside a Git checkout. Network reporting is opt-in through DEVWF_MONITOR_URL, and the broader agent configuration setup runs only when explicitly invoked.
Evidence
.state/workflow-state.jsonOpenCode configuration path resolved by scripts/setup-stack.jsAGENTS.md in the directory passed to ensureAgentsMd
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 script initializes the package’s workflow state under the installing project’s .state directory.
- The prepare script skips Husky setup when the package directory is not a Git checkout.
- The stack setup edits OpenCode configuration and installs its components only when the setup script is run directly.
- Monitor reporting is disabled unless DEVWF_MONITOR_URL is set; the reported snapshot contains workflow metadata rather than file contents.
Evidence against
- The postinstall hook creates a project state directory and file automatically.
- When configured, monitor reporting can send project path, task description, and machine name to the configured endpoint.
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.2.
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.2 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.