registry / @programinglive/dev-workflow-mcp-server / 1.23.11
@programinglive/dev-workflow-mcp-server@1.23.11
MCP server to enforce development workflow discipline
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe automatic postinstall action creates the package’s workflow state file, and the Husky prepare helper skips registry installs without a Git checkout. The broader agent configuration and related downloads are confined to explicit setup/bootstrap flows.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installation initializes workflow state; broader agent-stack setup requires an explicit setup command.
Impact
No harmful credential collection, unrelated data transmission, or concealed execution was found in the inspected paths.
Mechanism
The install hook writes a workflow state file. The separate setup command configures OpenCode and may create AGENTS.md when directly invoked.
AI rationale
The automatic postinstall action creates the package’s workflow state file, and the Husky prepare helper skips registry installs without a Git checkout. The broader agent configuration and related downloads are confined to explicit setup/bootstrap flows.
Evidence
.state/workflow-state.jsonopencode.jsonAGENTS.md
Network endpoints2
github.comraw.githubusercontent.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs install.js.
- install.js initializes workflow state at .state/workflow-state.json and skips when the install path is inside node_modules.
- Agent-stack configuration is a separate setup command; its setup code runs only when invoked directly.
- The prepare helper skips Husky installation when the package directory is not a Git checkout.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
11 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 High6 Medium6 Low
CriticalPrevious Version Dangerous Deltatools/handler-modules/index.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
MediumDynamic Requiresecurity/log-bridge.cjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/verify-orphan-cleanup.sh
Affected versions and remediation
This report applies to @programinglive/dev-workflow-mcp-server@1.23.11.
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.23.11 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.