registry / @programinglive/dev-workflow-mcp-server / 1.13.7
@programinglive/dev-workflow-mcp-server@1.13.7
MCP server to enforce development workflow discipline
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe postinstall hook creates a blank workflow state file in the invoking project and leaves an existing file untouched. OpenCode configuration and plugin changes belong to a separate setup command, and the inspected source shows no malicious data collection or transmission.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs postinstall; OpenCode and RTK setup runs only when the setup script is directly invoked.
Impact
Automatic behavior creates a blank workflow state file. No credential collection, unrelated network contact, or harmful account action was identified.
Mechanism
The install hook creates .state/workflow-state.json if it does not exist. The separate setup command can register plugins and update OpenCode configuration.
AI rationale
The postinstall hook creates a blank workflow state file in the invoking project and leaves an existing file untouched. OpenCode configuration and plugin changes belong to a separate setup command, and the inspected source shows no malicious data collection or transmission.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.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 runs install.js, which initializes a workflow state file in the invoking project.
- The install script checks for an existing state file and writes a blank initial workflow state when none exists.
- Global OpenCode setup and plugin registration are implemented in a separate setup script that runs when directly invoked.
Evidence against
- The package declares prepare and postinstall lifecycle scripts.
- The separate setup script can modify OpenCode configuration and register plugins when run.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemShell
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 High4 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
MediumEnvironment Vars
MediumShips Build Helperscripts/setup-test-dbs.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptofactory-client.js
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.13.7.
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.13.7 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.