registry / @programinglive/dev-workflow-mcp-server / 1.19.20
@programinglive/dev-workflow-mcp-server@1.19.20
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook initializes a missing project-local state file, while broader agent configuration changes require the explicit setup command. Monitoring is disabled unless a URL is configured and reports workflow metadata rather than file contents.
Static reason
One or more suspicious static signals were detected.
Trigger
The npm postinstall hook initializes state; setup-stack runs when the user invokes the setup command; monitor reports require DEVWF_MONITOR_URL to be set.
Impact
The reviewed behavior matches the package’s workflow-management purpose; no automatic credential collection, unrelated data transfer, or concealed execution was found.
Mechanism
Installation creates an absent .state/workflow-state.json. Explicit setup edits OpenCode configuration and may create AGENTS.md. Monitoring sends workflow metadata to the configured URL.
AI rationale
The install hook initializes a missing project-local state file, while broader agent configuration changes require the explicit setup command. Monitoring is disabled unless a URL is configured and reports workflow metadata rather than file contents.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
Network endpoints3
DEVWF_MONITOR_URL (user-configured)github.com/obra/superpowers.gitraw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh
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 creates a project-local workflow state file only when it is absent; it does not send data.
- The setup script’s AGENTS.md and OpenCode configuration changes run only when the user invokes the setup command.
- Runtime monitor reports are disabled unless DEVWF_MONITOR_URL is configured, and the payload contains workflow metadata rather than file contents.
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/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.20.
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.20 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.