How a developer ends up here

Public GitHub data only, measured over the last 7, 30 and 90 days. No account is ranked against another and no number combines these into one.

Open work, in one field

This archive follows one patch of ground: coding agents, terminal tooling, agent frameworks and the open repositories developers actually build with. A project reaches it only by clearing the same relevance bar as every other story here, so the people in this index are the ones behind open work in that space. What put somebody here is a thing they made that other developers found worth using, never anything about them.

And no popularity bar

How many people have starred a repository shows on a profile as a fact about that repository. It is neither a threshold to clear nor a sort key, so a small project that solved a real problem for other developers can be the whole reason somebody appears here, and a large one confers nothing extra.

The anchor

Every candidate starts as a link. A signal note already in this archive cites a GitHub repository, and the account that owns or pushes to it becomes somebody the pipeline knows about. Nothing here is discovered by going looking for people.

One hop

The pipeline then asks those same repositories who else builds them. Exactly one hop, never two, and how many commits each person has is thrown away at that boundary rather than carried forward, since it decides nothing later.

The hand-written few

A short list of logins is written into a config file by hand. They clear the same floors as everybody else and their record says plainly that no account check was ever made for them, because being on somebody’s list is not a measurement.

Three floors, no arithmetic

One: at least one signal note in this archive, or there is no page. That is the answer to “why is this person here”. Two: fewer than five active days in ninety gets a label saying so and is never removed, because thin data about somebody is a fact about the data rather than about them. Three: an account whose activity has the shape of automation is held back, and one with a recorded verdict against it is out. The three are independent and each is reported on the profile in its own words. There is no sum and no weighting, because a combined number would be a judgement of a person wearing a decimal point.

The order, and why it is not volume

The default order is how many separate days an account pushed on. Ordering by raw volume was measured and abandoned: it puts automation and mass-repository activity far above people doing ordinary careful work, which makes the list a measure of machinery rather than of anything worth reading. Consistency is the one thing the underlying feed supports.