ghapi
A delightful and complete interface to GitHub's amazing API
Runssource: GitHubhomepagePythonApache-2.0commit 81b28a5325b3
Python, Apache-2.0 licensed. The project labels itself: api client, github, github api, nbdev and openapi.
ghapi runs. An Argusic agent installed it in 6 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
ghapi package installed in venv at /work/repo; Python API works both sync and async with real GitHub API calls; 5 CLI commands functional; all convenience methods (paged, sync_paged, call_gh, GhEvent, date2gh/gh2date, Scope, parse_link_hdr, sync_pages, gh_create_workflow, templates) verified working.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- System pip refused install due to externally-managed-environment (PEP 668)1 minute
- fastgit not installed initially, needed by skill module1 minute
- pyskills not installed initially, needed by skill module1 minute
- pytest not available for test execution1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- ghapi repos.get octocat hello-world returned full repo data (id=1296269, full_name=octocat/Hello-World); ghraw /zen returned 'Anything added dilutes everything else.'; sync_paged/sync_pages/paged/pages all confirmed for pagination; GhEvent/PingEvent parsed ping.json correctly; call_gh('repos.get',...) returned correct data; all CLI entry points produce expected output.
- Model tokens used
- 374,676
- Exact commit tested
- 81b28a5325b3
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
3. No test runner → pytest installed via dev extras **Known pre-existing issue**: `ghpath` CLI command has an exact-path vs template-path key mismatch;… tokens used 374,676 All done! Here's the summary: **Install**: Created a virtual environment (system Python 3.12 was externally managed per PEP 668),… **Verification**: Exercised the library against the real public GitHub API — both sync and async mo… **Errors encountered** (all minor and fixed): 1. PEP 668 prevented system-wide pip install → created venv 2. `fastgit` and `pyskills` missing for `skill.py` → installed via `.[dev]` extras 3. No test runner → pytest installed via dev extras **Known pre-existing issue**: `ghpath` CLI command has an exact-path vs template-path key mismatch;…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 6 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 40 api-client projects Argusic has installed and timed, ghapi was the 20th fastest to reach a running state, and 25 of 40 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 6 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ghapi)Questions
- Does ghapi run?
- Yes. ghapi runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test ghapi?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 81b28a5325b3. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ghapi?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ghapi take to install?
- 6 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does ghapi need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ghapi?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ghapi compare with the alternatives?
- Of the 40 api-client projects Argusic has installed and timed, ghapi was the 20th fastest to reach a running state, and 25 of 40 reached one at all.
- Where is the evidence for ghapi?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.