Build a GitHub-compatible git forge

$500 reward. Opens . Ends . What to build: Build a standalone GitHub-compatible git forge: no UI, one process that serves git smart HTTP, the REST v3 API, GraphQL and MCP from its own store. Reward bar: A reward needs a score better than the best house entry's. An entry that does not beat it keeps its spot in the ranking but earns no reward. Each bounty's rules give the exact bar.

Needs Node 22: Node 22 runs the kit's local suite and your entry the way the grader runs it; nothing else is installed.

Full brief

GitHub is a git host and an API that agents already know how to use: clone and push over smart HTTP, repositories and issues over the REST v3 API, queries over GraphQL, and tools over MCP. Build a standalone forge that serves all four from one process and its own store, with no UI and no outside service, and we grade it with a sealed suite that drives it as a client while four timed workloads measure how fast it answers.

Context

The suite is the same for every entry. It pushes commits and clones them back, reads and writes repositories, issues, pull requests and contents through the REST v3 API, runs GraphQL queries and mutations of the shape gh and github-mcp-server send, and speaks MCP to your tools. Its checks report pass or fail into an export that must be the same across two runs. Four workloads time it: 200 pushes, 50 concurrent shallow clones, 2,000 issue reads and 200 issue writes.

Practice instances are published in the kit, and a local runner runs the same suite against your forge on your own machine. In the final, three scored instances are drawn after the deadline and nobody, the organisers included, can know them while entries are taken.

Deliverables

  • A public GitHub repository owned by your own GitHub account, created after the competition opens, under an OSI-approved license, with main.ts (Node 22) or main.py (Python 3.13) in the repository root that starts your forge as one process
  • The AI coding-agent transcripts of the sessions that built it (Claude Code, Codex, Cursor and others), uploaded with each submission
  • No user interface: the suite, not a browser, is the client

Requirements

  • Node 22 or Python 3.13, the standard library plus source you vendor into the repository: nothing is installed before the program runs, and there is no git binary, package manager or outside service
  • One process: it binds an ephemeral port of its own, registers that port with the suite, serves from its own store, and never binds 8080, which the suite listens on
  • Deterministic: two runs on the same instance must leave the same state export, byte for byte; keep every time out of that state
  • At most 16 MiB of source in all and 8 MiB in any one file, a vendored git library or a statically linked binary included
  • The house enters the reference forge as a house entry in the last hours: it always goes on to the final whatever it scores and takes none of the 60 seats, a prize needs a score above it (a statistical tie with it does not beat it), and it holds the place it finishes in and never takes that place's prize
  • At most 5 submissions a day and 10 in all; your last submission before the deadline is your final entry