Control from a unix domain socket
Metadata
Current evaluation
Feature request to allow fetch service to listen on a unix-domain socket for improved security. Unlabelled, no comments, inactive for 390 days.
Suggested action: needs triage
Reason: The issue has no labels, no comments, and no assignee despite being 551 days old. It is a legitimate feature request from a maintainer (lengau) to improve security by allowing unix-domain socket support for the fetch service, but it has not yet been triaged or acknowledged by the team. The 390-day inactivity period warrants triage to determine if this is still relevant or has been superseded.
Impact:
55
Quick Win:
30.25
Staleness:
75
Complexity:
45
Confidence:
60
Support Request:
0
Issue body
### What needs to get done
Allow the fetch service to listen on a unix-domain socket if a socket path is provided.
### Why it needs to get done
This allows craft applications to control the server without making it available on the network.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b |
Impact:
55
Quick Win:
30.25
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 issues
No related issues found above the similarity threshold.