registry / @programinglive/dev-workflow-mcp-server / 1.14.0
@programinglive/dev-workflow-mcp-server@1.14.0
MCP server to enforce development workflow discipline
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged lifecycle hooks perform local workflow-state initialization and conditional Husky setup. The setup script that modifies agent configuration is user-invoked, and Factory network requests require configured Factory credentials and explicit tool calls; no malicious collection, concealed execution, or unauthorized account action was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm install runs the lifecycle hooks; the OpenCode setup and Unix bootstrap run when explicitly invoked; Factory requests follow calls to Factory tools when credentials are configured.
Impact
No automatic credential or project-data exfiltration or unrelated account action was found. User-invoked setup changes agent configuration, and configured Factory calls disclose task/device details to the selected Factory service as part of the integration.
Mechanism
The postinstall hook creates a missing project workflow-state file. The optional setup command registers the MCP server and plugin and updates OpenCode configuration. Configured Factory calls send Factory credentials to the configured Factory service.
AI rationale
The flagged lifecycle hooks perform local workflow-state initialization and conditional Husky setup. The setup script that modifies agent configuration is user-invoked, and Factory network requests require configured Factory credentials and explicit tool calls; no malicious collection, concealed execution, or unauthorized account action was found.
Evidence
.state/workflow-state.jsonOpenCode opencode.json configurationAGENTS.md~/.config/programinglive-factory/device.json
Network endpoints4
FACTORY_URL (operator-configured)pocketbase.programinglive.comgithub.com/obra/superpowers.gitraw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook initializes a missing workflow state file in the invoking project; it skips creating that file when the project root is inside node_modules.
- OpenCode integration setup runs only when scripts/setup-stack.js is invoked directly, such as through the declared setup command.
- Factory tools require the operator to configure a Factory URL and credentials, and network requests occur when those tools are called.
- Factory requests send the Factory token as a Bearer credential to the configured Factory URL.
- The Unix bootstrap script’s RTK download-and-run path is an explicit setup step and uses RTK’s GitHub release repository.
Evidence against
- The manifest has prepare and postinstall hooks, but the inspected hook code performs local setup rather than contacting a collector or transmitting project data.
- The setup script writes agent configuration and registers integrations, but its setup routine is guarded against import-time execution.
- The Factory integration uses Factory-specific credentials and is inactive until configured and invoked.
Behavioral surface
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 High4 Medium6 Low
CriticalPrevious Version Dangerous Deltatools/handler-modules/index.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
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.14.0.
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.14.0 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.