registry / @programinglive/dev-workflow-mcp-server / 1.13.14
@programinglive/dev-workflow-mcp-server@1.13.14
MCP server to enforce development workflow discipline
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe install hooks perform limited setup for the package's workflow purpose, and the more extensive agent configuration changes require an explicit setup command. The reviewed source does not show an attack chain or unrelated data collection.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm install for workflow-state creation; direct invocation of scripts/setup-stack.js for agent-stack setup.
Impact
Expected workflow setup and state tracking; no source evidence of credential collection, unrelated data transfer, or hidden agent control changes.
Mechanism
The postinstall hook creates .state/workflow-state.json if absent. The explicit setup script updates OpenCode configuration and may create AGENTS.md.
AI rationale
The install hooks perform limited setup for the package's workflow purpose, and the more extensive agent configuration changes require an explicit setup command. The reviewed source does not show an attack chain or unrelated data collection.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package has prepare and postinstall scripts, whose behavior was reviewed.
- The postinstall hook creates a workflow state file in the installer's project; it skips when INIT_CWD points inside node_modules and preserves an existing state file.
- The prepare script skips Husky setup outside a Git checkout.
- The changed commit handler checks that Git is operating in the requested repository before proceeding.
- The agent-stack setup runs only when its script is invoked directly.
Evidence against
- The package performs install-time filesystem writes, but the reviewed write is limited to workflow state for the package's stated purpose.
- The explicit setup command can modify OpenCode configuration and create AGENTS.md; this is user-invoked setup behavior.
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 Deltatools/handler-modules/commit-handlers.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
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.13.14.
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.14 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.