registry / @programinglive/dev-workflow-mcp-server / 1.23.6
@programinglive/dev-workflow-mcp-server@1.23.6
MCP server to enforce development workflow discipline
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe install-time write is limited to an empty workflow state file that supports the package’s stated purpose. Network reporting is disabled by default, and broader agent setup is an explicitly invoked, documented command.
Static reason
One or more suspicious static signals were detected.
Trigger
The postinstall hook runs during installation. Monitoring occurs during runtime only when configured; stack configuration requires an explicit setup command.
Impact
The install hook adds a project state file. Configured monitoring shares workflow metadata with the operator-selected service; no malicious behavior was identified.
Mechanism
The install hook creates an empty .state/workflow-state.json in the invoking project. Runtime monitoring sends workflow metadata to DEVWF_MONITOR_URL when set.
AI rationale
The install-time write is limited to an empty workflow state file that supports the package’s stated purpose. Network reporting is disabled by default, and broader agent setup is an explicitly invoked, documented command.
Evidence
<projectRoot>/.state/workflow-state.jsonOpenCode opencode.json (explicit stack setup)<projectRoot>/AGENTS.md (explicit stack setup, if absent)
Network endpoints3
DEVWF_MONITOR_URL (operator-configured)github.com/obra/superpowers.git (explicit stack setup)raw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh (bootstrap fallback)
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook initializes an empty workflow state file in the invoking project; it does not send data or contact a host.
- The separate agent-stack setup runs only when directly invoked, and its README describes its configuration changes.
- Runtime monitoring is disabled when DEVWF_MONITOR_URL is unset and sends workflow metadata only to the configured URL.
- The package’s documented purpose is workflow state tracking and MCP server operation.
Evidence against
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.6.
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.6 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.