registry / @programinglive/dev-workflow-mcp-server / 1.23.4
@programinglive/dev-workflow-mcp-server@1.23.4
MCP server to enforce development workflow discipline
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe install hooks perform local workflow-state initialization and conditional Git-hook setup. The agent-stack changes are documented and run only through an explicit setup command; no malicious behavior was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs the local state initializer; Husky setup requires a Git checkout. Broader agent setup requires an explicit command.
Impact
No unsolicited credential collection, unrelated network contact, or automatic agent-configuration write was identified.
Mechanism
Lifecycle code writes workflow state locally. The separately invoked setup script registers the documented OpenCode stack and creates AGENTS.md if missing.
AI rationale
The install hooks perform local workflow-state initialization and conditional Git-hook setup. The agent-stack changes are documented and run only through an explicit setup command; no malicious behavior was identified.
Evidence
install.jsscripts/install-husky.jsscripts/setup-stack.js
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook initializes a local `.state/workflow-state.json` file and skips when installation runs inside `node_modules`.
- The prepare hook skips Husky setup unless the package directory is a Git checkout.
- The broader OpenCode and AGENTS.md setup runs only when `scripts/setup-stack.js` is invoked directly, and the README documents that command and its effects.
- The MCP server starts only when `index.js` is run directly.
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/verify-orphan-cleanup.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.23.4.
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.23.4 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.