registry / @programinglive/dev-workflow-mcp-server / 1.19.16
@programinglive/dev-workflow-mcp-server@1.19.16
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe lifecycle hooks perform package-related setup: creating an idle workflow state file and installing Husky only in a Git checkout. Broader OpenCode and AGENTS.md changes are confined to an explicitly invoked setup script, and no malicious behavior was found in the inspected entry points.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs the prepare and postinstall hooks; scripts/setup-stack.js and scripts/bootstrap-unix.sh require explicit invocation.
Impact
The install hook adds workflow state to the invoking project. The inspected source showed no automatic credential theft, unrelated data transmission, or install-time agent configuration changes.
Mechanism
The postinstall hook creates an idle .state/workflow-state.json if absent. The separately invoked setup script registers OpenCode components and may create AGENTS.md.
AI rationale
The lifecycle hooks perform package-related setup: creating an idle workflow state file and installing Husky only in a Git checkout. Broader OpenCode and AGENTS.md changes are confined to an explicitly invoked setup script, and no malicious behavior was found in the inspected entry points.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
Network endpoints3
github.com/obra/superpowers.gitopencode.ai/config.jsonraw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh
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 initializes an idle workflow state file under the npm invocation directory, and the installer skips writing when that file already exists.
- The prepare hook's Husky installer exits when the package is not in a Git checkout.
- OpenCode and AGENTS.md configuration changes are performed by setup-stack.js only when that script is run directly.
- The MCP server uses a stdio transport; no automatic credential collection or unrelated data transmission was identified.
Evidence against
- The postinstall hook creates a .state directory and workflow-state.json in the invoking project.
- The explicitly run setup script can edit OpenCode configuration and create AGENTS.md; the bootstrap helper can install RTK.
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/setup-test-dbs.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.19.16.
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.19.16 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.