registry / @programinglive/dev-workflow-mcp-server / 1.23.8
@programinglive/dev-workflow-mcp-server@1.23.8
MCP server to enforce development workflow discipline
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe lifecycle hooks have limited, local purposes: postinstall initializes workflow state, and prepare conditionally installs Husky in the package’s Git checkout. The flagged dependency installation, OpenCode configuration changes, and RTK download occur only through user-run setup or bootstrap commands, and no malicious data flow or concealed behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs postinstall; the prepare script runs during applicable npm operations. Broader setup runs only when the user invokes the setup or bootstrap command.
Impact
The install hook may create a local workflow state file in the invoking project. No credential collection, unrelated network contact, or other attack behavior was found.
Mechanism
Postinstall creates an initial .state/workflow-state.json if absent. Prepare conditionally invokes the local Husky binary in the package checkout. The explicit setup command installs dependencies and configures OpenCode; bootstrap may install RTK from its official GitHub host.
AI rationale
The lifecycle hooks have limited, local purposes: postinstall initializes workflow state, and prepare conditionally installs Husky in the package’s Git checkout. The flagged dependency installation, OpenCode configuration changes, and RTK download occur only through user-run setup or bootstrap commands, and no malicious data flow or concealed behavior was found.
Evidence
.state/workflow-state.json~/.config/opencode/opencode.json~/.config/opencode/secrets/opencode-backup-<timestamp>.jsonAGENTS.md
Network endpoints1
raw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall script creates a default workflow state file in the invoking project and skips when installed inside node_modules; it makes no network request.
- The prepare script skips outside a Git checkout and runs the local Husky installer when one is present.
- The setup script’s dependency installation, OpenCode configuration edits, and agent setup run through the explicit setup command.
- The bootstrap script can download RTK’s installer from its official GitHub host when a user runs the bootstrap.
Evidence against
- The package declares prepare and postinstall lifecycle scripts.
- The setup command can install dependencies and write OpenCode configuration and an AGENTS.md file.
- The bootstrap script contains a download-and-run command for RTK’s official installer.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
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.8.
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.8 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.