registry / @programinglive/dev-workflow-mcp-server / 1.13.13
@programinglive/dev-workflow-mcp-server@1.13.13
MCP server to enforce development workflow discipline
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe lifecycle behavior initializes local workflow state, and Husky setup is limited to Git checkouts. The broader OpenCode configuration changes are gated behind an explicit setup command; the reviewed Factory credential refresh reads that service's own configuration for its Factory integration.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
npm postinstall creates initial project workflow state; global agent setup runs only when the user invokes the setup command.
Impact
No source evidence of credential theft, unrelated data collection, concealed execution, or unrequested account actions.
Mechanism
Writes a local state file and, on explicit setup, registers the MCP server and related configuration.
AI rationale
The lifecycle behavior initializes local workflow state, and Husky setup is limited to Git checkouts. The broader OpenCode configuration changes are gated behind an explicit setup command; the reviewed Factory credential refresh reads that service's own configuration for its Factory integration.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
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 script initializes a workflow state file in the npm caller's project; this matches the package's workflow-state purpose.
- The prepare script skips Husky setup unless the package is in a Git checkout.
- Global OpenCode setup is exposed as a direct setup command and runs only when the setup script is invoked directly.
- Factory credentials are reread from the named OpenCode server configuration during Factory authentication, and the default PocketBase host is the package's Factory service.
Evidence against
- The postinstall hook writes `.state/workflow-state.json` in the npm caller's project.
- The explicit setup command can modify OpenCode configuration and create an AGENTS.md file in the target project.
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.13.13.
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.13 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.