registry / @programinglive/dev-workflow-mcp-server / 1.23.1
@programinglive/dev-workflow-mcp-server@1.23.1
MCP server to enforce development workflow discipline
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe postinstall hook creates the workflow state file the package uses, and the prepare hook limits Husky setup to a Git checkout. The flagged AI-stack configuration and related setup actions require direct invocation.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation creates project workflow state; AI-stack configuration runs only when its setup script is directly invoked.
Impact
The reviewed automatic install behavior is limited to initializing workflow state in the invoking project.
Mechanism
The installer writes .state/workflow-state.json. The separate setup script configures OpenCode and agent instructions when explicitly run.
AI rationale
The postinstall hook creates the workflow state file the package uses, and the prepare hook limits Husky setup to a Git checkout. The flagged AI-stack configuration and related setup actions require direct invocation.
Evidence
.state/workflow-state.json
Network endpoints3
github.comopencode.airaw.githubusercontent.com
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 hook runs install.js; that script skips state creation when INIT_CWD is inside node_modules.
- The installer writes an initial workflow-state.json file for the invoking project, matching the package’s workflow-state purpose.
- The prepare hook skips Husky setup when the package directory is not a Git checkout.
- The AI-stack setup script runs setupStack only when invoked directly, so its agent and OpenCode configuration changes are user-triggered.
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.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.23.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.