registry / @programinglive/dev-workflow-mcp-server / 1.19.14
@programinglive/dev-workflow-mcp-server@1.19.14
MCP server to enforce development workflow discipline
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe postinstall hook creates an initial workflow state file in the invoking project, which matches the package's workflow-state purpose. The shell and agent-configuration actions are in setup utilities that require explicit invocation, and the inspected install path shows no data transfer.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs the postinstall hook; the broader stack setup requires direct invocation.
Impact
A local state file may be added to the project; no malicious data collection or transfer was identified.
Mechanism
install.js creates .state/workflow-state.json under INIT_CWD (or the current directory) with initial workflow fields.
AI rationale
The postinstall hook creates an initial workflow state file in the invoking project, which matches the package's workflow-state purpose. The shell and agent-configuration actions are in setup utilities that require explicit invocation, and the inspected install path shows no data transfer.
Evidence
projectRoot/.state/workflow-state.json
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 hook runs install.js.
- The install hook initializes a local workflow state file under the invoking project directory.
- The prepare helper skips Husky setup when the package is not in a Git checkout.
- The stack setup routine runs only when its script is invoked directly.
Evidence against
- Postinstall automatically creates .state/workflow-state.json in the invoking project directory.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
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
6 High6 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
MediumDynamic Requiresecurity/log-bridge.cjs
MediumNetwork
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.19.14.
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.19.14 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.