registry / @programinglive/dev-workflow-mcp-server / 1.19.15
@programinglive/dev-workflow-mcp-server@1.19.15
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe install hook creates only local workflow state, while runtime monitoring is off unless a user configures `DEVWF_MONITOR_URL`. The flagged setup and download behavior is confined to explicitly invoked setup scripts and uses the named tools’ expected sources.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation runs the postinstall initializer; workflow reporting occurs during runtime only when configured; stack setup and bootstrap require explicit invocation.
Impact
No unauthorized data collection, credential theft, or unrelated automatic actions were identified.
Mechanism
The initializer creates a project-local state file. The monitor sends workflow metadata to the configured endpoint. Setup modifies OpenCode configuration and can install the RTK tool when explicitly run.
AI rationale
The install hook creates only local workflow state, while runtime monitoring is off unless a user configures `DEVWF_MONITOR_URL`. The flagged setup and download behavior is confined to explicitly invoked setup scripts and uses the named tools’ expected sources.
Network endpoints2
raw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh (explicit bootstrap)github.com/obra/superpowers.git (explicit setup)
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 a project-local `.state/workflow-state.json` and leaves an existing state file intact.
- Runtime monitor reporting is disabled unless `DEVWF_MONITOR_URL` is set, and its documented payload is workflow metadata rather than file contents.
- The OpenCode stack setup runs only when its script is invoked directly; its config and agent setup are explicit setup behavior.
- The bootstrap script downloads the RTK installer from its official GitHub host only when the user runs the bootstrap and RTK is missing.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
11 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 High6 Medium6 Low
CriticalPrevious Version Dangerous Deltaworkflow-state.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
MediumDynamic Requiresecurity/log-bridge.cjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/setup-test-dbs.sh
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.19.15.
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.15 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.