@programinglive/dev-workflow-mcp-server@1.9.1
MCP server to enforce development workflow discipline
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found no malicious behavior. The lifecycle hooks initialize local workflow state or conditionally set up Git hooks; OpenCode configuration changes are reachable through the explicit setup command.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package runs its declared lifecycle hooks; the OpenCode and agent setup runs when a user invokes the setup command.
Impact
The inspected behavior supports the package’s workflow and agent setup, with no confirmed attack effect.
Mechanism
The postinstall hook creates a project-local workflow state file. The explicit setup command configures OpenCode integrations and creates AGENTS.md; the prepare helper skips outside a Git checkout.
AI rationale
Source inspection found no malicious behavior. The lifecycle hooks initialize local workflow state or conditionally set up Git hooks; OpenCode configuration changes are reachable through the explicit setup command.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
Network endpoints1
github.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes setup as an explicit command; its postinstall hook only calls install.js to create project-local workflow state.
- prepare calls a Husky helper that skips when the package is not in a Git checkout.
- The setup routine writes the OpenCode configuration and creates AGENTS.md as part of the requested setup flow; its agent configuration behavior is reachable through that explicit command.
- The inspected dependencies provide MCP protocol and stdio code, dotenv configuration loading, and SQLite binding code; the SQLite install script invokes native build setup.
- The shared execution helper selects a repository working directory for workflow commands.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 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 } from "child_process";
L2: import { existsSync } from "fs";
High
Findings
5 High5 Medium5 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
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/bootstrap-unix.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Low
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.9.1.
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.9.1 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.