h2o
reference corpus · status live · domain NET (Networking, protocols and serialisation) · lane A · refresh pinned · tags GLOBAL · HTTP · HTTP2 · SERVER · C · PERFORMANCE
What an agent uses it for
An agent implementing a high-performance HTTP/1-2 server queries this for event-loop request handling, HTTP/2 prioritization, and header processing in C.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/h2o.jsonxerj corpus add --from ./h2o.jsonxerj corpus index h2o then xerj code h2o "your question"Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "h2o", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| h2o | d21e7cb56258 | MIT | 30.2 MB / 8,573 files | licence host-verified (ok-spdx): MIT |
30.2 MB across 8,573 files. Added 2026-10-13.
Rights
MIT. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.
Retrieval spot-check (G7)
Not yet spot-checked. Queries are pre-registered in the registry before grading.