Live Score
Paste a public GitHub repository URL for a score based on what an agent can find, read, and run in it — the same numbers the leaderboard uses. Scored on the spot from the current commit, and stored nowhere.
GitLab and Bitbucket support coming.
Past scores
Questions
- Does the repo have to be on the leaderboard?
- No — that is the point of this page. Paste any public GitHub repository URL and it is scored on the spot, whether or not we have ever indexed it. Repos already on the leaderboard redirect to their permanent page instead, which carries the same numbers plus score history.
- How is this different from the leaderboard's own scores?
- It is not. Both run the same scorer over the same signals and weights; they differ only in how the files get there. The leaderboard clones each repo on a six-hourly cron, while this page reconstructs the repository from GitHub's tree API at request time. A CI job asserts the two produce identical numbers on a fixture set chosen for the ways they could disagree.
- Is my repository stored or listed anywhere?
- No. A live score is computed, rendered, and discarded — nothing about the repository is written to the database, and scoring a repo never adds it to the public leaderboard. The result page is marked noindex, so it will not turn up in search. The list of repos you have scored is kept in your own browser and never sent anywhere.
- How fresh is the score?
- It is computed from the repository's current commit, and the page shows the short SHA it used. Results are cached per URL for an hour, so a push made minutes ago may not be reflected until the cache turns over.
- Does it work on private repos, GitLab, or Bitbucket?
- Public GitHub repositories only, for now. Private repos would need authorization we deliberately do not ask for. GitLab and Bitbucket are implemented and score identically to a clone, but are held back until their API limits are guarded — GitLab paginates its tree at 100 entries and Bitbucket allows 60 unauthenticated requests an hour. To score a private repo today, run the agent skill locally instead.
- Why did a very large repository refuse to score?
- Reconstructing a tree of several hundred thousand entries would take longer than a request can run, so past a ceiling the page declines rather than timing out or returning a partial score. The agent skill scores those locally with no such limit.