@programinglive/dev-workflow-mcp-server@1.19.3
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package's explicit setup command changes global OpenCode settings and registers external agent integrations, which is broader than configuring this package alone. The reviewed install hooks do not exfiltrate data, and monitor reporting is disabled unless the user configures an endpoint.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs `npm run setup` or directly invokes scripts/setup-stack.js.
Impact
These changes expand or alter the user's agent plugins and integrations at the global configuration level.
Mechanism
The script registers a third-party plugin, adds this MCP server to OpenCode configuration, and initializes RTK's global OpenCode integration.
AI rationale
The package's explicit setup command changes global OpenCode settings and registers external agent integrations, which is broader than configuring this package alone. The reviewed install hooks do not exfiltrate data, and monitor reporting is disabled unless the user configures an endpoint.
Evidence
package.jsonscripts/setup-stack.jsconfigDir/opencode.jsonconfigDir/plugins/configDir/secrets/opencode-backup-{timestamp}.jsontargetProjectRoot/AGENTS.md
Network endpoints3
github.com/obra/superpowers.gitopencode.ai/config.jsonDEVWF_MONITOR_URL (user-configured; /api/session and /api/event)
Decision evidence
public snapshotAI called this Suspicious at 78.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The setup command modifies the global OpenCode configuration.
- Setup registers the Superpowers plugin from GitHub.
- Setup runs RTK initialization with global OpenCode options.
- The setup routine runs when its script is invoked directly, including through the package's `setup` command.
Evidence against
- The broad configuration changes require an explicit setup command; they are not performed by the package's import or install hooks.
- The postinstall hook creates a local workflow state file and does not send data.
- Runtime monitor reporting is disabled unless the user sets DEVWF_MONITOR_URL.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
11 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
1 Critical6 High6 Medium6 Low
CriticalPrevious Version Dangerous Deltaworkflow-state.js
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
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.19.3.
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.3 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.