# Schweinepriester/github-profile-achievements: the reference list of GitHub profile badges > A Markdown repository that catalogues every GitHub profile Achievement, its earn criteria and its tiers, plus the internal and disabled ones. It is documentation, not a tool, and its value depends on how closely GitHub's undocumented thresholds are tracked. **Schweinepriester/github-profile-achievements** — A collection listing all Achievements available on the GitHub profile 🏆 - Repository: https://github.com/Schweinepriester/github-profile-achievements - Stars: 5,071 · Forks: 452 - Language: Markdown - License: MIT - Published: 2026-09-23 · Updated: 2026-09-23 · Language: en - Canonical page: https://hysenlabs.com/projects/schweinepriester-github-profile-achievements ## What the GitHub achievements list actually is GitHub introduced an Achievements section on user profiles in 2021, starting with the Mars 2020 Helicopter Mission badge, the Arctic Code Vault badge and a badge for sponsoring open source work through GitHub Sponsors. Schweinepriester/github-profile-achievements exists to enumerate those badges in one place. The repository is Markdown, not software. Its top level holds .gitattributes, LICENSE, README.md and an images directory, and the README is the product. The audience is narrow but real. People who want to know which badges exist, what triggers each one, and how many repetitions move a badge from base to Bronze, Silver or Gold. The README also separates three categories that most summaries blur together: earnable achievements, internal achievements awarded for contributions to GitHub's own development, and disabled achievements that were live at some point but no longer appear on profiles. That last category is the reason the list stays useful after GitHub changes things. A badge you remember seeing on a profile in 2022 may simply be disabled now, and the README says so instead of leaving you to guess. ## How the achievement tables are organised The README is a set of Markdown tables with four columns: Title, Badge, Earnable, and Earned by. The Earnable column carries a check mark or a cross, and the internal and disabled tables add qualifiers such as "(Internal)" or "(Being tested)". Badge images are referenced from the images directory, including a tiers subdirectory for the Bronze, Silver and Gold variants. The Earned by column is where the substance sits. Pair Extraordinaire comes from coauthoring a commit in a merged pull request. Quickdraw comes from closing an issue or pull request within five minutes of opening it. Starstruck comes from creating a repository that reaches 16 stars. Galaxy Brain needs 2 accepted answers, Pull Shark needs 2 merged pull requests, YOLO comes from merging your own pull request without code review. The tier table gives the escalating numbers: Starstruck x2 at 128 stars, x3 at 512, x4 at 4096; Pair Extraordinaire x2 at 10 coauthored merges, x3 at 24, x4 at 48. Some rows are deliberately incomplete. Heart On Your Sleeve Gold is listed with unknown reaction counts, and both Heart On Your Sleeve and Open Sourcerer are marked as being tested. That honesty is more useful than a confident guess, but it also means you cannot treat the table as a complete specification. GitHub announced additional achievements in June 2022 without publishing specific criteria, and the README asks readers to open an issue when something is missing or wrong. The list is community-maintained by design. ## Using the list: no installation, just reading and checking There is no package to install and no binary to run. The README gives no install steps because the repository has none. You consume it by reading the tables on the repository page or by cloning it if you want the badge images locally. If you want a local copy, the standard Git commands apply: ```bash git clone https://github.com/Schweinepriester/github-profile-achievements.git cd github-profile-achievements ``` After cloning you get the Markdown README plus the images directory, so the badge PNGs render without hitting GitHub's servers. Nothing else is required; the repository has no build step, no dependency manifest and no test suite. The first real use is looking up a single badge. Search the README for the title, read the Earned by cell, and then check the tier table if the badge has tiers. For example, if you are chasing Starstruck, the base row says 16 stars and the tier rows say 128, 512 and 4096. If you want to hide achievements entirely, the README points to GitHub's own documentation on changing the visibility of achievements and gives a direct link to the profile settings page, which is the setting that controls whether badges appear at all. That link is the closest thing to an action the repository offers. ## Where the catalogue stops being authoritative This is a documentation project tracking a closed system. GitHub does not publish a stable, versioned specification of Achievements, and the README admits as much: the June 2022 announcement added achievements without specific criteria. Any number in the table is therefore a community observation that can drift when GitHub changes a threshold or retires a badge. The disabled table shows how fast that happens. Heart On Your Sleeve and Open Sourcerer are listed as disabled and being tested, so they are neither earnable nor visible on profiles right now. If you build anything on top of these criteria, such as a progress tracker or a dashboard, you are depending on undocumented behaviour that GitHub can change without notice. The README also does not document rollback, migration or notification when a badge's criteria change; the only signal is a commit to the repository. A second limitation is scope. The repository covers profile Achievements only. It says nothing about other GitHub badges, contribution graphs, or the mechanics of GitHub Sponsors beyond the Public Sponsor achievement row. If your question is about anything other than the achievement badges, this is the wrong place to look. ## Compared with the GitHub Blog and the Community discussions The obvious alternative is GitHub's own material. The GitHub Blog posts announced the Achievements section and the later batch of achievements, and those posts are the primary source. The difference in approach is that the blog announces; it does not maintain a table. It will not tell you that Starstruck Gold needs 4096 stars, and it will not keep a disabled section for badges that no longer render. The other alternative was GitHub's Community Discussions, where achievements were discussed until February 2024, when GitHub removed them from Community Discussions to counter spam. That removal is itself an argument for a repository like this one: the discussion venue disappeared, so a versioned Markdown file with a commit history is the more durable record. What the repository cannot match is GitHub's authority. When the blog and the README disagree, the blog wins, and the README's issue tracker is where that disagreement is supposed to be resolved. ## Maintenance, licensing and what a fork costs you The repository is not archived, and its last push was on 2026-05-22, which is when release v4.0.0 ("The unachievable five") was published. The previous release, v3.0.0 ("Nice nine"), dates to 2022-11-09, and v2.0.0 to 2022-07-13. That cadence tells you what to expect: long quiet periods punctuated by a release when enough has changed to justify one. Do not expect a steady stream of small updates. The licence is MIT, which permits reuse, modification and redistribution provided the copyright notice and permission notice are retained. For a Markdown table and a folder of badge images, that is about as permissive as it gets. One caveat worth naming without giving legal advice: the badge artwork in the images directory originates from GitHub, and the repository's MIT licence covers the repository's contents as published, not any trademark or brand rights GitHub may hold in the badge designs. If you plan to redistribute the images in a product, that distinction is worth checking. The upgrade cost is near zero in the technical sense, since there is nothing to build. The real cost is editorial: if you mirror this list, you own keeping it in sync with a source that changes on GitHub's schedule, not yours. A fork that is not re-checked when a new release lands will quietly become wrong, and the failure is silent because a stale table looks exactly like a current one. ## Conclusion Adopt this repository if you need a single, citable list of GitHub profile Achievements, their tiers and the badges that no longer appear on profiles, and if you are willing to check the commit history rather than trust the README alone. Do not adopt it as an installable tool, an unlocker or an API: there is no code to run, the repository is a Markdown table and an images directory, and the README does not document any automation. Before relying on a specific threshold, verify it against the table and the linked GitHub announcement, because several criteria in the README are marked as unknown or still being tested. ## FAQ ### How do you get achievements on GitHub? The README lists the trigger for each badge. Examples include coauthoring a commit in a merged pull request for Pair Extraordinaire, closing an issue or pull request within five minutes for Quickdraw, creating a repository that reaches 16 stars for Starstruck, and merging your own pull request without code review for YOLO. ### What is a GitHub profile used for? The repository does not explain profile purpose beyond the Achievements section, which GitHub added in 2021 starting with the Mars 2020 Helicopter Mission badge, the Arctic Code Vault badge and a badge for sponsoring open source work through GitHub Sponsors. The README's focus is the badges themselves, not the profile as a whole. ### Why would someone need a GitHub account? The README does not address account creation or its benefits. It only documents the Achievements available on a GitHub profile and how each badge is earned, and it links to GitHub's own documentation for changing the visibility of achievements. ## Sources - [Issues](https://github.com/Schweinepriester/github-profile-achievements/issues) - [License: MIT](https://github.com/Schweinepriester/github-profile-achievements/blob/main/LICENSE) - [README](https://github.com/Schweinepriester/github-profile-achievements/blob/main/README.md) - [Releases](https://github.com/Schweinepriester/github-profile-achievements/releases) - [Schweinepriester/github-profile-achievements on GitHub](https://github.com/Schweinepriester/github-profile-achievements) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/schweinepriester-github-profile-achievements