registry / @programinglive/dev-workflow-mcp-server / 1.19.18
@programinglive/dev-workflow-mcp-server@1.19.18
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook initializes a missing workflow state file in the invoking project, while the prepare helper skips outside a Git checkout. Broader OpenCode and agent configuration changes are tied to the package's explicit setup command, and the reviewed sources show no malicious data flow or unauthorized account action.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs postinstall; prepare may run in applicable installs. OpenCode configuration setup runs through the explicit setup command.
Impact
The reviewed behavior supports the package's workflow and setup purpose; no unauthorized collection, credential transfer, or hidden account action was identified.
Mechanism
The postinstall script initializes a missing project workflow state file. The setup command registers the MCP server and plugin and may write OpenCode configuration and AGENTS.md.
AI rationale
The install hook initializes a missing workflow state file in the invoking project, while the prepare helper skips outside a Git checkout. Broader OpenCode and agent configuration changes are tied to the package's explicit setup command, and the reviewed sources show no malicious data flow or unauthorized account action.
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 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest identifies an MCP workflow tool; its main and bin entry point is index.js, with prepare and postinstall hooks.
- The postinstall script uses INIT_CWD or the current directory and skips state creation when the path is inside node_modules.
- The install script creates .state/workflow-state.json only when it does not already exist.
- The prepare helper skips husky setup unless the package is in a Git checkout.
- The broader OpenCode and agent configuration changes belong to the separately invoked setup command, which runs setupStack only when directly executed.
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/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.18.
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.18 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.