registry / @programinglive/dev-workflow-mcp-server / 1.10.0
@programinglive/dev-workflow-mcp-server@1.10.0
MCP server to enforce development workflow discipline
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe lifecycle hooks perform limited workflow setup, and broader agent configuration changes require the explicit setup command. Factory credentials are used by the configured Factory integration; inspected source establishes no attack behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation initializes workflow state; running the setup command configures OpenCode and may add an agent instruction file.
Impact
The inspected behavior supports the package's workflow and integration features; no harmful effect was established.
Mechanism
The install hooks create workflow state or set up Git hooks. Factory network calls require configured credentials and an invoked Factory tool.
AI rationale
The lifecycle hooks perform limited workflow setup, and broader agent configuration changes require the explicit setup command. Factory credentials are used by the configured Factory integration; inspected source establishes no attack behavior.
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest runs a state initializer after installation and a Git-aware Husky setup during prepare; the initializer skips installs inside node_modules and creates only a workflow state file in the invoking project.
- The OpenCode and agent configuration changes belong to the separately invoked setup command; it registers the documented tools and creates AGENTS.md only when one is absent.
- Factory requests require configured credentials and an invoked Factory tool; password authentication goes to the configured PocketBase endpoint and the resulting token goes to the configured Factory URL.
- The MCP runtime uses the SDK's standard server and stdin/stdout transport; the inspected SDK, SQLite, and dotenv dependency excerpts show ordinary entry, native-build, and environment-loading behavior.
Evidence against
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 } from "child_process";
L2: import { existsSync } from "fs";
High
Findings
1 Critical5 High4 Medium6 Low
CriticalPrevious Version Dangerous Deltascripts/verify-bundle.mjs
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
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.10.0.
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.10.0 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.