@programinglive/dev-workflow-mcp-server@1.23.9
MCP server to enforce development workflow discipline
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package's automatic postinstall only initializes workflow state, and no malicious data collection or execution was identified. Its explicit setup command also modifies broader agent configuration, so users should be warned about that capability.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs `npm run setup` or directly executes `scripts/setup-stack.js`.
Impact
OpenCode behavior and project agent instructions change beyond this package's MCP server settings.
Mechanism
The setup script updates OpenCode configuration, registers a plugin and MCP server, and may create project-level `AGENTS.md` instructions.
AI rationale
The package's automatic postinstall only initializes workflow state, and no malicious data collection or execution was identified. Its explicit setup command also modifies broader agent configuration, so users should be warned about that capability.
Evidence
package.jsonscripts/setup-stack.jsopencode.jsonAGENTS.md
Network endpoints1
github.com
Decision evidence
public snapshotAI called this Suspicious at 79.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The setup command is explicitly exposed as `npm run setup` and runs `scripts/setup-stack.js`.
- The setup script writes to OpenCode's configuration and registers plugins and an MCP server.
- Setup creates an `AGENTS.md` file in the target project when one does not exist.
- The automatic postinstall initializes a project workflow state file.
Evidence against
- The setup script runs only when invoked directly.
- The postinstall state file contains initial workflow fields; the inspected code shows no network transmission.
- The setup actions are consistent with the script's stated purpose of configuring an AI development stack.
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/verify-orphan-cleanup.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.23.9.
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.23.9 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.