@programinglive/dev-workflow-mcp-server@1.13.6
MCP server to enforce development workflow discipline
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe postinstall hook can create a project file automatically when this package is installed as a dependency. The write is related to the package’s workflow purpose and no data transmission was found, so this is a warning-level install hook concern rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the postinstall hook automatically.
Impact
Unexpectedly adds a hidden state directory and file to the consumer’s project during installation; no exfiltration was identified.
Mechanism
`install.js` resolves `INIT_CWD` as the project root, then creates `.state/workflow-state.json` if it does not already exist.
AI rationale
The postinstall hook can create a project file automatically when this package is installed as a dependency. The write is related to the package’s workflow purpose and no data transmission was found, so this is a warning-level install hook concern rather than a block.
Evidence
package.jsoninstall.js<INIT_CWD>/.state/workflow-state.json
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Unknown with high false-positive risk.
Evidence for warning
- `package.json` runs `node install.js` as a postinstall hook.
- `install.js` uses `INIT_CWD` as the project root and creates `.state/workflow-state.json` there during installation.
- The `node_modules` guard only skips when `INIT_CWD` itself contains `node_modules`, so a normal consumer project path does not meet that condition.
- The broader OpenCode setup and `AGENTS.md` write are in `setup-stack.js`, which runs only when that script is invoked directly.
Evidence against
- The postinstall file contains only initial workflow-state fields; the reviewed code does not send that state over the network.
- The package describes itself as a development workflow MCP server, so a workflow state file is related to its purpose.
- The setup script’s global agent configuration changes require a separate direct invocation.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemShell
HighEntropyStrings
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.6.
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.6 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.