bilannoun, Frencha balance sheet; an assessment of a situation, as in faire le bilan, to take stock.
See what is actually moving in a repository: who is contributing, which areas are changing, how reviews flow, and where work gets stuck. And as AI-assisted coding changes how much gets opened, how big it is, and how much of it is really reviewed, this is where you watch that shift over time.
Read-only on your own GitHub token. Open source. No sign-in needed for the examples.
More, and more useful, numbers than GitHub shows about a repository’s activity, for any window of time. The figures below are withastro/astro’s last 30 days.
Who opens pull requests and who reviews them, which areas of the codebase are moving week by week, down to each package of a monorepo, and which areas rest on a single person.
139pull requests opened by 60 authors
Time to a first review and time to merge, as medians and p90s, week by week, so a slow week shows up as a slow week.
1.6hmedian wait for a first review · 75% of pull requests reviewed
How reviews spread across people, each reviewer’s turnaround, and the reviewer–author pairs that hold most of the knowledge.
169reviews given by 12 reviewers
Ready pull requests with no review for days, approved work that never merged, old drafts, and anything else that stands out, flagged as worth a look.
67pull requests still open · p90 time to merge 13d
bilan uses no AI. It measures what AI-assisted coding does to a repository: how much gets opened, how big it is, how fast it merges, how much of it carries a real review, and where the review load lands on the people. Compare any window with the one before it and the shift is there in the numbers.
Pull requests opened per week and the size distribution: whether more, larger changes are arriving, and whether the long tail grows.
139opened in 30 days by 60 authors
Reviews per reviewer, the share the top three carry, and the wait for a first review: whether the humans reviewing keep up.
75%of pull requests ever reviewed · first review in 1.6h
Merges without a review from anyone else, and revert pull requests, week by week: what gets through without a second pair of eyes.
Bot-authored pull requests as a share of the whole, with their own merge rate and lead time, kept apart from the people.
Full-history snapshots shipped with bilan, open to anyone. They are not live: sign in to sync a repository of your own.
The Astro web framework: a large monorepo with a core team and a long tail of community contributors.
Last 30 days of the snapshot
Wrangler and the Workers SDK: a busy monorepo where bots open a fair share of the pull requests.
Last 30 days of the snapshot
A number is only useful if the people it describes agree with how it was counted. bilan makes three choices, and shows its working for each.
A draft is work in progress, not a request for review. Time to first review and time to merge are measured from the moment a pull request is marked ready; time in draft is reported on its own line.
“Last 30 days” means what happened in those 30 days: merges when they merged, reviews when they were given. A comparison with the previous period appears only once that period is synced.
Per-person numbers are there to show where review load pools, which pairs hold the knowledge, and which areas rest on one person, so a team can change how work flows. It is not a leaderboard, and there is no score.
Where review time starts
The median pull request in withastro/astro over the last 30 days of its snapshot.
Each metric is counted by its own event
A date range scopes every line by its anchor, so a pull request opened in August and merged in September counts as opened in August and merged in September.
| Metric | Anchored at | How it is measured |
|---|---|---|
| PRs opened | created | Counted when the PR is opened. |
| Merged, closed unmerged | merged / closed | Counted when it lands or is closed. |
| Merged PRs by area | merged | Per area and week, or month over all time; a PR counts in every area it touched. |
| Time in draft | created | Opened → marked ready, for PRs opened as drafts. |
| Time to first review | ready | Ready → first review by someone other than the author. |
| Time to merge | merged | Ready → merged. |
| Reviewer turnaround | review | Review request (or ready, if never requested) → that reviewer’s first review. |
| Reviews given | review | Counted when submitted; self-reviews excluded. |
| Review threads per PR | merged | Review threads per merged PR, by size. Threads opened by bot reviewers count too. |
| Approved with no threads | merged | Every review was an approval, and no review thread was opened. |
| Time to approval | merged | Ready → first approval, by size. |
bilan is a GitHub App with two read-only permissions, pull requests and metadata. There is no scope to grant and nothing it could write with.
Choose Start sync to read the last 30 days and every open pull request on your own token, usually in under a minute. Longer ranges sync when you ask for them.
The result is cached once. Anyone who can already see the repository on GitHub opens the same dashboard; anyone else gets a page that reveals nothing.
An organization owner installs the app once from GitHub; anyone else can request it. Access is checked against each viewer’s own token.
npx github-bilan owner/name --openThe CLI syncs a repository into a local cache and writes one self-contained HTML report: styles, script, and data in a single file you can open offline, attach to an issue, or archive.
It talks to the GitHub API and nothing else. Nothing leaves your machine: the cache lives in ~/.cache/bilan, and re-runs only fetch what changed.
The token comes from --token, then GITHUB_TOKEN, GH_TOKEN, or gh auth token. The default depth is the last 30 days plus every open pull request.
| Flag | What it does |
|---|---|
| --open | Open the report in the browser when it is written. |
| --out FILE | Where to write the report. Default: <name>.report.html. |
| --since DATE | Reach back to DATE. Coverage only ever widens. |
| --full | Walk the entire history. |
| --max-prs N | Stop after N pull requests in this run. |
| --offline | Render from the local cache without calling GitHub. |
| --no-cache | Ignore the cache and fetch everything again. |
| --token T | Use this token instead of the environment. |
| --areas FILE | List the folders that count as areas, nested ones included. |