The Methodology.

What we read

GLYPH connects to your public GitHub history and reads six signals. Everything on your card comes from these and nothing else.

1. 01

   Contribution volume

   GitHub's own contribution count for the last year. It is the number on your contribution graph, which counts commits alongside pull requests, issues and reviews — GLYPH calls it commits throughout the product, and that is a simplification worth knowing about here.

2. 02

   Streak

   Longest and current runs of consecutive contribution days, derived from the same calendar. Longest measures the habit at its best; current measures whether it is running now.

3. 03

   Stars received

   Total stars across your public repositories, and stars per repository. A signal that other people found something worth keeping.

4. 04

   Repository shape

   How many public repositories you have, and how finished they are — whether each carries a README, a licence, and a deployment or homepage. Used to tell a folder of experiments from a shelf of shipped things.

5. 05

   Language distribution

   Percentage breakdown by bytes across your public repositories, plus the top languages by share. Shows technical surface area, not depth.

6. 06

   Followers

   Your public follower count. Used in exactly one rule, and never in rarity.

How archetypes work

Your archetype comes from a deterministic ruleset — not machine learning, not randomness. The same GitHub history always produces the same archetype.

The rules are checked in order, and the first match wins. That ordering is part of the result: an account that qualifies for three archetypes receives whichever sits highest in the table below. Rarity is computed separately and never affects which archetype you get.

Archetypes are determined by your public GitHub signals only. They describe patterns in your observable output — not your ability, your intelligence, or your professional value.

How rarity works

Rarity is a threshold on contribution volume, with one exception. Mythic is the only tier that asks for more than commits: it needs volume, stars and a long streak together. Everything below it is decided by volume alone.

Rarity is not a measure of engineering skill. A senior engineer whose work sits in private repositories will have fewer public contributions than a student with abundant free time. GLYPH knows this and is honest about it.

What GLYPH doesn’t know

The three lines

The three-line description on your card is written by Claude, Anthropic’s AI. It is given your archetype, rarity and headline numbers, and writes a short description of the pattern. Your email address, avatar and access token are never sent.

It is creative writing, not analysis. It is meant to feel true — not to be cited as evidence of anything.

Can you game GLYPH?

Yes. Someone could make many small, trivial commits to inflate their count. Someone could star their own repositories from other accounts. Because the contribution count includes issues and pull requests, those can be padded too.

We know this. GLYPH is not a hiring assessment. It is a developer identity card built from public signals — closer to a Spotify Wrapped than a performance review. The same way playing one song a hundred times shapes your Wrapped, padding commits shapes your GLYPH.

If you do that, your card will reflect it. Whether that bothers you is between you and your code.

This version

• AlgorithmGLYPH v1.0
• ReleasedSeptember 2026
• Archetypes12, deterministic, first match wins
• Rarity tiers5, threshold-based
• Flavour textClaude Sonnet (Anthropic)
• Data sourceGitHub GraphQL API, read-only
• OAuth scoperead:user, user:email, public_repo

The scope is the narrowest that works: public_repo cannot return a private repository, so “public data only” is enforced by the permission itself rather than by our good intentions. If you authorised GLYPH before September 2026 you will be asked to approve the smaller scope the next time you sign in.