llm-cli-gateway 1.17.0 → 1.17.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,18 @@ All notable changes to the llm-cli-gateway project.
4
4
 
5
5
  ## Unreleased
6
6
 
7
+ ## [1.17.1] - 2026-05-30 — Socket shell-access suppression
8
+
9
+ Patch release updating the package's Socket policy for the reviewed gateway
10
+ process-launching capability.
11
+
12
+ ### Changed
13
+
14
+ - Suppressed Socket's `shellAccess` alert in `socket.yml` now that the
15
+ child-process surface is documented and release-audited.
16
+ - Updated README Socket-alert wording so reviewers still get the bounded
17
+ shell-access rationale without seeing the same package alert on every release.
18
+
7
19
  ## [1.17.0] - 2026-05-30 — upstream provider tracking
8
20
 
9
21
  Feature release adding repeatable upstream-provider contract tracking for the
package/README.md CHANGED
@@ -1176,7 +1176,7 @@ The gateway supports concurrent requests across different CLIs. Each request spa
1176
1176
 
1177
1177
  ### Socket alerts — context for reviewers
1178
1178
 
1179
- If you're vetting `llm-cli-gateway` through [Socket](https://socket.dev/npm/package/llm-cli-gateway) or a similar supply-chain scanner, you'll see three behavioural alerts and some dependency-ownership alerts. They are accurate descriptions of what the package does and what it depends on; we've left them visible (not silenced in `socket.yml`) so you don't have to take our word for it. Here's the context for each:
1179
+ If you're vetting `llm-cli-gateway` through [Socket](https://socket.dev/npm/package/llm-cli-gateway) or a similar supply-chain scanner, you'll see behavioural alerts and some dependency-ownership alerts. They are accurate descriptions of what the package does and what it depends on. The reviewed `shellAccess` capability is suppressed in `socket.yml` to avoid a repeat finding on every release; the rationale remains documented here and in the package.
1180
1180
 
1181
1181
  | Alert | Where | Why it's bounded |
1182
1182
  | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "llm-cli-gateway",
3
- "version": "1.17.0",
3
+ "version": "1.17.1",
4
4
  "mcpName": "io.github.verivus-oss/llm-cli-gateway",
5
5
  "description": "MCP server providing unified access to Claude Code, Codex, Gemini, Grok, and Mistral Vibe CLIs with session management, retry logic, async job orchestration, durable job results, and cross-LLM validation.",
6
6
  "license": "MIT",
package/socket.yml CHANGED
@@ -2,11 +2,9 @@ version: 2
2
2
 
3
3
  # Socket alerts on llm-cli-gateway
4
4
  # ---------------------------------
5
- # This package intentionally triggers three of Socket's behavioural alerts.
6
- # We do NOT disable them they are accurate descriptions of what the package
7
- # does, and silencing them would hide useful signal from anyone evaluating
8
- # this dependency. The rationale for each is documented inline below and in
9
- # detail under "Security Considerations" in README.md.
5
+ # This package intentionally triggers behavioural alerts. They are accurate
6
+ # descriptions of what the package does; the rationale for each is documented
7
+ # inline below and in detail under "Security Considerations" in README.md.
10
8
  #
11
9
  # networkAccess
12
10
  # src/http-transport.ts opens an HTTP MCP transport (createServer/listen).
@@ -23,9 +21,10 @@ version: 2
23
21
  #
24
22
  # shellAccess
25
23
  # This alert fires on every module that imports node:child_process, and
26
- # because spawning provider CLIs and git is the entire purpose of the
27
- # package it surfaces on every release BY DESIGN we keep it visible
28
- # rather than silencing it. It is a capability description, not a finding.
24
+ # because spawning provider CLIs and git is the entire purpose of the package
25
+ # it is a reviewed capability description, not a finding. As of v1.17.1 this
26
+ # specific reviewed alert is suppressed via `issueRules.shellAccess: false`
27
+ # to avoid noisy repeat findings on every release.
29
28
  #
30
29
  # INVARIANT enforced across ALL sites below: arguments are always passed
31
30
  # as an array and `shell: true` is NEVER set, so there is no shell
@@ -75,6 +74,7 @@ issueRules:
75
74
  installScripts: true
76
75
  telemetry: true
77
76
  hasNativeCode: true # better-sqlite3 — known and expected
77
+ shellAccess: false # reviewed gateway capability; see rationale above
78
78
  shellScriptOverride: true
79
79
  gitDependency: true
80
80
  httpDependency: true