registry / @programinglive/dev-workflow-mcp-server / 1.13.12
@programinglive/dev-workflow-mcp-server@1.13.12
MCP server to enforce development workflow discipline
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe postinstall hook only initializes the package’s workflow state in the invoking project. Network and agent-configuration behavior belongs to explicit setup or configured Factory operations, with no evidence of unrelated data collection or hidden actions.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation creates workflow state; OpenCode and RTK setup requires running the setup script; Factory network calls require configuration and a tool request.
Impact
The install hook adds a local state file; explicit setup changes OpenCode configuration. No unrelated collection, concealed execution, or unrequested account action was identified.
Mechanism
The install hook creates a local state file. The explicit setup script registers the server and plugin. Configured Factory calls use supplied credentials with the configured service or the default PocketBase service.
AI rationale
The postinstall hook only initializes the package’s workflow state in the invoking project. Network and agent-configuration behavior belongs to explicit setup or configured Factory operations, with no evidence of unrelated data collection or hidden actions.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
Network endpoints3
raw.githubusercontent.compocketbase.programinglive.comFACTORY_URL (configured by the user)
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook creates an empty workflow state file in the invoking project and leaves an existing file untouched.
- The package’s Factory integration returns no configuration unless a Factory URL and credentials are supplied through environment variables.
- The setup script’s OpenCode configuration and plugin changes run through an explicit setup command.
- The bootstrap script offers RTK installation from its project’s GitHub host when a user runs it.
Evidence against
- Installation does modify the invoking project by creating `.state/workflow-state.json`.
- The explicit setup command writes OpenCode configuration and can register an external plugin.
- When configured, Factory requests send the supplied credentials to the configured service or the package’s default PocketBase host.
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.12.
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.12 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.