registry / @programinglive/dev-workflow-mcp-server / 1.15.0
@programinglive/dev-workflow-mcp-server@1.15.0
MCP server to enforce development workflow discipline
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe automatic postinstall path only initializes a missing workflow state file in the invoking project. The broader OpenCode and RTK setup is available through an explicit setup command, and the inspected source showed no malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm install runs postinstall; global agent-stack configuration runs only through npm run setup.
Impact
The install hook adds workflow state to the invoking project. No credential collection, unrelated data transmission, or concealed execution was identified.
Mechanism
The postinstall script creates a missing project .state/workflow-state.json file. The setup command configures OpenCode and RTK.
AI rationale
The automatic postinstall path only initializes a missing workflow state file in the invoking project. The broader OpenCode and RTK setup is available through an explicit setup command, and the inspected source showed no malicious behavior.
Evidence
.state/workflow-state.jsonAGENTS.md~/.config/opencode/opencode.json~/.config/opencode/secrets/opencode-backup-<timestamp>.json
Network endpoints3
github.comopencode.airaw.githubusercontent.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs install.js, which creates a missing .state/workflow-state.json file in the invoking project.
- The install script skips state-file creation when INIT_CWD points inside node_modules.
- The OpenCode stack setup is exposed as an explicit npm run setup command.
- The main entrypoint starts the MCP server only when invoked directly.
Evidence against
- The package has an automatic postinstall hook that writes into the invoking project.
- The explicit setup command edits global OpenCode configuration and may install or configure related tools.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemShell
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
1 Critical6 High4 Medium6 Low
CriticalPrevious Version Dangerous Deltaindex.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
MediumEnvironment Vars
MediumShips Build Helperscripts/setup-test-dbs.sh
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
Low
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.15.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.15.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.