NousResearch/hermes-agent

Health endpoint missing API key auth requirement

Cluster 90315 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
5items grouped
Known?
Yes. 5 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

A bug was identified where the GET /health route on the API server did not enforce API_SERVER_KEY authentication, unlike other routes. Multiple related fixes address requiring the key on that endpoint when configured.

Open issues1

  • Issue#90315[Bug]: API server GET /health ignores API_SERVER_KEY while other routes require it

Open PRs1

  • PR#90421fix(api): require API_SERVER_KEY on GET /health

3 PRs closed without merging

From the close comments: duplicate 3

  • #90676 fix(api-server): require API_SERVER_KEY on GET /health when configured · duplicate → #90421
  • #90724 fix(api): require API_SERVER_KEY auth on GET /health (#90315) · duplicate → #90421
  • #93957 fix(api_server): /health honors API_SERVER_KEY like every other route · duplicate → #90421
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
0
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.