Control from a unix domain socket
Metadata
Current evaluation
Feature request: let the fetch service control API (currently TCP-only, bound to all interfaces via --control-port) also listen on a unix-domain socket when a path is given. Still open, no labels, no discussion.
Suggested action: needs triage
Reason: Confirmed unimplemented at HEAD: control/control.go still hardcodes `Addr: fmt.Sprintf(":%d", port)` with `ListenAndServe()`, and `Options`/`CmdlineOptions` only expose `ControlPort` (int) — no socket path option exists anywhere. The request is valid hardening (the control API is bound to all interfaces, mitigated only by basic auth from FETCH_SERVICE_AUTH), and service/fetchctl/server.go plus commits a394475/82cedba (#190/#191) show a unix-socket precedent to follow. But the issue carries zero labels, zero comments and no maintainer triage since 413 days ago, and it states no CLI flag name, socket permission policy, or whether it replaces or coexists with the TCP port — so it still needs triage rather than being treated as ready-to-implement.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
15
Complexity:
40
Confidence:
82
Actionability:
55
|
needs triage | Feature request: let the fetch service control API (currently TCP-only, bound to all interfaces via --control-port) also listen on a unix-domain socket when a path is given. Still open, no labels, no discussion. | |
| stealth/space-bunny-alpha |
Impact:
52
Quick Win:
20
Complexity:
43
Confidence:
74
Actionability:
66
|
needs triage | Unix-domain socket support for the fetch service remains an open, untriaged feature request to avoid exposing server control on the network. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
19
Complexity:
40
Confidence:
78
Actionability:
76
|
needs triage | Allow the fetch service to listen on a Unix-domain socket when configured, avoiding network exposure. This maintainer-authored enhancement remains untriaged, with no labels or discussion. | |
| qwen/qwen3.6-35b-a3b |
Impact:
55
Quick Win:
30
Staleness:
75
Complexity:
45
Confidence:
60
Support Request:
0
|
needs triage | Feature request to allow fetch service to listen on a unix-domain socket for improved security. Unlabelled, no comments, inactive for 390 days. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
fetch-service#190
(confidence 55%)
Commit a394475 'feat(service): add configuration socket server (#190)' added a unix-socket server (service/fetchctl/server.go, with SocketPath() cleanup) — an in-repo precedent for unix socket listening, though it serves a different custom protocol than the HTTP control API.
Related issues
No related issues found above the similarity threshold.