registry / @programinglive/dev-workflow-mcp-server / 1.19.11
@programinglive/dev-workflow-mcp-server@1.19.11
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged lifecycle scripts perform package-related setup, and the network reporting path is disabled unless the user configures DEVWF_MONITOR_URL. I found no automatic credential collection, unrelated data transfer, or concealed execution.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs the lifecycle scripts; monitoring sends only after workflow activity when DEVWF_MONITOR_URL is set. Stack configuration and update checks require explicit commands.
Impact
No malicious behavior identified. If enabled, monitoring shares project paths and task descriptions with the endpoint configured by the user.
Mechanism
The postinstall script creates an initial state file. Optional monitoring posts workflow metadata to the configured URL. The explicit setup command configures OpenCode and agent workflow files.
AI rationale
The flagged lifecycle scripts perform package-related setup, and the network reporting path is disabled unless the user configures DEVWF_MONITOR_URL. I found no automatic credential collection, unrelated data transfer, or concealed execution.
Evidence
$INIT_CWD/.state/workflow-state.jsonOpenCode configDir/opencode.jsonOpenCode configDir/secrets/opencode-backup-<timestamp>.json$INIT_CWD/AGENTS.md
Network endpoints4
DEVWF_MONITOR_URL (user-configured; no default host)raw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.shgit+https://github.com/obra/superpowers.gitregistry.npmjs.org/@programinglive/dev-workflow-mcp-server/latest
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 creates an initial workflow state file in the invoking project and skips when the install path is inside node_modules.
- Monitor reporting is disabled when DEVWF_MONITOR_URL is unset; when enabled, it sends workflow metadata to that configured endpoint.
- The setup script runs its configuration changes only when invoked directly, such as through the explicit setup command.
- The update checker documents that it does not check the network automatically while the MCP server runs.
Evidence against
- The postinstall hook writes .state/workflow-state.json in the invoking project.
- When monitor reporting is enabled, its payload includes project paths and task descriptions.
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.11.
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.11 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.