registry / @programinglive/dev-workflow-mcp-server / 1.14.1
@programinglive/dev-workflow-mcp-server@1.14.1
MCP server to enforce development workflow discipline
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe lifecycle scripts perform workflow-related initialization and Git-checkout setup, with no install-time network contact or harmful execution found. The broader agent configuration changes are behind a separate user-invoked setup command.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install initializes missing project state; OpenCode setup requires the separate setup command.
Impact
The observed default install side effect is limited to workflow state initialization; no harmful data collection or execution was found.
Mechanism
The install hook creates `.state/workflow-state.json` if absent. The explicit setup command edits OpenCode configuration and may register plugins and agent instructions.
AI rationale
The lifecycle scripts perform workflow-related initialization and Git-checkout setup, with no install-time network contact or harmful execution found. The broader agent configuration changes are behind a separate user-invoked setup command.
Evidence
<projectRoot>/.state/workflow-state.json<configDir>/opencode.json<configDir>/plugins/<INIT_CWD>/AGENTS.md
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest separates the `setup` command from the `postinstall` hook, which runs `install.js`.
- The postinstall initializer creates a missing `.state/workflow-state.json` in the invoking project and leaves an existing file alone.
- The Husky prepare script exits without action outside a Git checkout.
- The broader OpenCode setup runs only when `setup-stack.js` is directly invoked, such as through the separate setup command.
- Factory tools require a configured URL and credentials before using the Factory service.
Evidence against
- Installation does create project state automatically; the separate setup command can also change OpenCode configuration and add agent setup files when explicitly 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.14.1.
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.14.1 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.