The badge

One card, generated from a person's GitHub record: a year of daily contributions, contributions and commits per active day with the bookkeeping stripped out, the peak day, and where the work sits between public and private repositories.

Put it on your profile

This is the block people paste into their own profile README. Replace LOGIN with your GitHub handle.

<div align="center">
  <a href="https://radar.id8.one/LOGIN">
    <picture>
      <source media="(prefers-color-scheme: dark)" srcset="https://radar.id8.one/LOGIN/badge-dark.png" />
      <img alt="LOGIN's Unlock Radar badge" src="https://radar.id8.one/LOGIN/badge-light.png" width="720" />
    </picture>
  </a>
</div>

Badges are generated by the radar pipeline from GitHub's records, and today they are issued on request, so ask for yours and it will be built for you. Self-serve is coming. Your history is kept only while the badge is on your profile, and it can be removed on request.

How to read it

• All contributions is not the same as commits. GitHub's calendar counts commits, pull requests, reviews and issues, so a pull request plus its commits counts several times. The badge shows contributions per active day and commits per active day side by side because they answer different questions.
• Substantive means the bookkeeping is removed. The second commit figure drops merge commits, automation-pattern commits such as release chores, version bumps and evidence rows, and micro-commits whose whole message is "x" or "wip". It is the fairer number, and it exists because raw commit counts flatter agent-driven work.
• The peak day is a raw calendar maximum. It can be a bulk event such as an import or a mass edit, so the same day is shown again counted in substantive commits.
• Momentum compares windows of 30 active days. The last 30 active days are measured against a baseline built from earlier windows. Two consecutive windows at twice baseline reads as sustained. One window reads as emerging.
• Every figure carries a provenance class. GitHub-served aggregate is the contribution calendar as GitHub computes it, public counts plus opted-in private ones. GitHub-served by repository is commit history read from GitHub's own copy of the repositories and deduplicated by SHA. A public-only figure is a floor, never a total, because the API will not expose another account's private repositories.

Who it is for

There is a ladder in how people work: at the bottom nobody is running agents, a step up an agent writes code under a person's hand, and a step up again the person has built a harness so the agent knows the codebase, the rules and the tests. At the top the person has largely stopped writing code and is conducting several agents at once, reviewing what comes back and deciding what ships. The radar exists to make that top rung visible from the outside, because it is the one rung that leaves no obvious artifact.

iD8 is the tool for the top of that ladder.