registry / @programinglive/dev-workflow-mcp-server / 1.19.31
@programinglive/dev-workflow-mcp-server@1.19.31
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook initializes the package’s workflow state, and the package’s broader OpenCode configuration is changed only by its explicit setup command. The normal server entry point connects over stdio; no malicious credential or data flow was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
Installation initializes workflow state; OpenCode stack setup requires a separate explicit command; server behavior starts when its entry point is run.
Impact
No credential collection, unrelated data transfer, or hidden install-time agent configuration change was identified.
Mechanism
The install hook creates a project-local state file. Explicit setup registers the MCP server and plugin in OpenCode configuration. The server uses stdio.
AI rationale
The install hook initializes the package’s workflow state, and the package’s broader OpenCode configuration is changed only by its explicit setup command. The normal server entry point connects over stdio; no malicious credential or data flow was identified.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.mdsecrets/opencode-backup-<timestamp>.json
Network endpoints3
github.comraw.githubusercontent.comopencode.ai
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest runs install.js during postinstall and exposes setup as a separate command.
- The install hook creates an initial project-local workflow state file.
- The OpenCode setup script writes configuration when explicitly run; it is not invoked by the package entry point.
- The server connects over stdio at startup.
Evidence against
- The package defines postinstall and prepare lifecycle scripts.
- The optional setup changes OpenCode configuration and may install the Superpowers plugin from GitHub.
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.31.
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.31 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.