@programinglive/dev-workflow-mcp-server@1.17.1
MCP server to enforce development workflow discipline
AI Security Review
scanned 4d ago · by lpm-firewall-aiNo automatic attack behavior was identified. The explicit setup command changes broader AI-agent settings by registering a third-party plugin and writing project instructions, so this warrants a warning for agent capability abuse.
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 invokes `scripts/setup-stack.js` directly.
Impact
These changes can alter which plugins, tools, and instructions the user's AI agent loads; the setup is disclosed and explicitly invoked, but it modifies broader agent settings.
Mechanism
The script registers the Superpowers GitHub plugin and this package as a local MCP server, then writes the OpenCode configuration and may create an AGENTS.md in the invoking project.
AI rationale
No automatic attack behavior was identified. The explicit setup command changes broader AI-agent settings by registering a third-party plugin and writing project instructions, so this warrants a warning for agent capability abuse.
Evidence
package.jsonscripts/setup-stack.jsinstall.jsOpenCode config directory/opencode.jsonOpenCode config directory/secrets/opencode-backup-*.jsonINIT_CWD/AGENTS.mdpackage projectRoot/node_modules
Network endpoints4
github.comopencode.airegistry.npmjs.orgraw.githubusercontent.com
Decision evidence
public snapshotAI called this Suspicious at 83.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The setup command adds a third-party OpenCode plugin and registers this package as a local MCP server in OpenCode configuration.
- Setup also writes an AGENTS.md file in the invoking project, changing the instructions an AI agent may follow.
Evidence against
- This configuration work runs through the explicit `npm run setup` command, not automatically on import or install.
- The postinstall script only creates an initial `.state/workflow-state.json` file when one does not already exist.
- The update checker is a separate command and is not run automatically by the MCP server.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
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
1 Critical6 High5 Medium6 Low
CriticalPrevious Version Dangerous Deltascripts/check-update.mjs
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
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/setup-test-dbs.sh
MediumStructural Risk Force Deep Review
Low
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.17.1.
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.17.1 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.