@programinglive/dev-workflow-mcp-server@1.13.5
MCP server to enforce development workflow discipline
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package's lifecycle hooks perform local setup, while the broader OpenCode configuration changes occur in an explicit setup command. Because that command changes global agent settings, classify it as a warning-level agent capability risk under the review rules.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs `npm run setup` or directly invokes `scripts/setup-stack.js`.
Impact
This changes which extensions OpenCode loads and adds workflow instructions for agents working in the project. The reviewed behavior is disclosed by the setup command and does not establish malicious intent.
Mechanism
The script registers a GitHub-hosted plugin and the MCP server globally, edits OpenCode configuration, and creates `AGENTS.md` in the target project.
AI rationale
The package's lifecycle hooks perform local setup, while the broader OpenCode configuration changes occur in an explicit setup command. Because that command changes global agent settings, classify it as a warning-level agent capability risk under the review rules.
Evidence
package.jsoninstall.jsscripts/setup-stack.jsconfigDir/opencode.jsonconfigDir/plugins/targetProjectRoot/AGENTS.mdstateDir/workflow-state.json
Network endpoints2
github.comraw.githubusercontent.com
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The package exposes setup as an explicit `npm run setup` command.
- That setup registers a third-party plugin from GitHub and registers the MCP server globally in OpenCode.
- The setup command edits OpenCode configuration and writes an `AGENTS.md` file in the target project.
- The postinstall hook creates a workflow state file under the installer's project directory.
Evidence against
- The global OpenCode setup runs only when the user invokes the setup command; it is not called by the lifecycle hooks or the package entry point.
- The postinstall write is limited to the package's workflow state file, and the script skips when `INIT_CWD` points inside `node_modules`.
- The inspected sources did not show automatic credential transmission, unrelated data collection, or review-directed instructions.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemShell
HighEntropyStrings
Source & flagged code
9 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 High4 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
MediumEnvironment Vars
MediumShips Build Helperscripts/setup-test-dbs.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptofactory-client.js
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.13.5.
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.13.5 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.