registry / @programinglive/dev-workflow-mcp-server / 1.16.0
@programinglive/dev-workflow-mcp-server@1.16.0
MCP server to enforce development workflow discipline
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe lifecycle hook creates a default local workflow state file and contains no network transmission. Agent configuration changes and the official RTK installer are part of explicit setup utilities, not hidden install-time behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs the postinstall state initializer; OpenCode and agent configuration changes require running the setup command.
Impact
Local setup files may be added. No credential collection, unrelated network contact, or concealed execution was found.
Mechanism
The postinstall hook creates a default .state/workflow-state.json if absent. The separate setup utility registers the local MCP server and plugin in OpenCode configuration and may create AGENTS.md.
AI rationale
The lifecycle hook creates a default local workflow state file and contains no network transmission. Agent configuration changes and the official RTK installer are part of explicit setup utilities, not hidden install-time behavior.
Evidence
<projectRoot>/.state/workflow-state.json<OpenCode configDir>/opencode.json<targetProjectRoot>/AGENTS.md
Network endpoints1
raw.githubusercontent.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook initializes workflow state in the consuming project and skips when INIT_CWD points inside node_modules.
- The state file is created only if it does not already exist; the hook does not send project data over the network.
- The setup script edits OpenCode configuration and creates AGENTS.md when explicitly run, and is guarded by a direct-run check.
- The bootstrap script's download-and-run fallback retrieves RTK's installer from its official GitHub repository.
Evidence against
- The package declares postinstall and prepare lifecycle scripts.
- The optional setup command writes OpenCode configuration and may create a project AGENTS.md file.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
9 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 High5 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
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/setup-test-dbs.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Crypto
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.16.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.16.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.