registry / @programinglive/dev-workflow-mcp-server / 1.13.3
@programinglive/dev-workflow-mcp-server@1.13.3
MCP server to enforce development workflow discipline
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe lifecycle hooks perform package-related setup: they initialize an empty workflow state file and skip Husky setup outside a Git checkout. Broader agent configuration changes are in a separate, directly invoked setup command.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm installation; broader OpenCode and AGENTS.md setup requires directly running the setup command.
Impact
No credential collection, unrelated network contact, or harmful account action was identified.
Mechanism
The postinstall script creates an empty `.state/workflow-state.json` in the invoking project if absent. The prepare script attempts Husky setup only when the package directory is a Git checkout.
AI rationale
The lifecycle hooks perform package-related setup: they initialize an empty workflow state file and skip Husky setup outside a Git checkout. Broader agent configuration changes are in a separate, directly invoked setup command.
Evidence
<INIT_CWD>/.state/workflow-state.jsonGit hooks in the package checkout, if present
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The automatic postinstall hook initializes workflow state in the project that invoked npm; it skips when that state file already exists.
- The state file contains workflow status fields and is written under `.state/workflow-state.json`.
- OpenCode and AGENTS.md setup is in a separate setup command that runs only when directly invoked.
Evidence against
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 Deltascripts/release.cjs
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.3.
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.3 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.