Why does GitHub count as evidence?
It counts because the Digital Technology assessors reward demonstrable technical contribution that others in the field actually use, and a well-run repository is one of the clearest proofs of that. Open-source work maps most naturally onto Optional Criterion 3 — a significant technical contribution to the field, and can also strengthen the mandatory criterion. The route requires the mandatory criterion plus at least two of the four optional criteria, so open source is rarely your whole case, but it can be a strong pillar of it.
What does "adoption and individual contribution" actually mean?
It means the assessor can see, from independent signals, both that the work is used beyond your own desk and that you personally built a meaningful part of it. Adoption is the external signal: stars, forks, downloads, dependent projects, issues raised by strangers. Individual contribution is the attribution signal: your merged pull requests, your commit history, your maintainer or reviewer role, a release you authored. GitHub is unusually good evidence because both signals are public and timestamped — you are not asking the assessor to take your word for it.
When does GitHub NOT count?
It fails when it shows neither adoption nor attributable individual work — and a raw profile link is the classic version of this. A profile with pinned repositories that nobody outside your employer uses, or a large project where your contribution is marginal, will not carry weight. This is a specific instance of a recurring refusal pattern reported by applicants and advisers: achievement stated at team level without individual attribution. Internal-only tools, forks with no original work, and tutorial-code dumps are the common weak forms. If the adoption is real but you cannot yet point to your own line of it, that is a gap to close before you apply — not something to paper over.
How do I evidence GitHub properly in the 10 documents?
You present it as a curated exhibit inside the evidence pack, not as a link and a hope. The Digital Technology route allows a maximum of 10 documents, each up to 3 sides of A4 (the CV and your three recommendation letters sit outside that count). A strong open-source exhibit typically pairs a screenshot or export showing the adoption metric — star count, download figures, dependent repositories — with a short, dated narrative naming the specific pull requests, features or releases you authored, and why they mattered. Where possible, have one of your recommendation letters corroborate the contribution. See the full 10-document evidence guide for how a pillar like this fits alongside the others.
How does the £200 Fit Assessment help?
It scores your GitHub and open-source material against the criteria before you spend anything on the Home Office, and tells you exactly where the adoption or attribution is thin. The Fit Assessment gives you a score out of 20, a component-by-component breakdown across the mandatory and optional criteria, a route recommendation between Exceptional Talent and Exceptional Promise, a 10-document evidence plan, and a 45-minute review call. If your open-source case is strong, you will know; if it is not yet, you will know what to fix. The £200 is credited in full to any package within 14 days.
Not sure your GitHub is enough on its own?
Get it scored against the real criteria before you spend £766 in government fees.
Frequently asked questions
Yes. GitHub and open-source work count when they show demonstrable adoption and your own individual contribution — repository stars, maintainer or core-committer status, and merged pull requests to projects others depend on. A bare profile link, on its own, does not count. Verify current criteria on GOV.UK.
Open-source contribution most naturally supports Optional Criterion 3 (a significant technical contribution to the field), and can also strengthen the mandatory criterion. You must meet the mandatory criterion plus at least two of the four optional criteria. Verify on GOV.UK.
There is no published star threshold. What matters is that the adoption is real and external — used beyond your own employer — and that your individual role in it is clearly attributable. A smaller project you clearly led can be stronger than a large project where your contribution is marginal.
Point to your own merged pull requests, your commit history, your maintainer or reviewer role, and any release you authored. The recurring refusal pattern is achievement stated at team level without individual attribution, so name what you personally built and how it was adopted.
Related reading: OC3 technical contributions, individual impact vs company success, the mandatory criterion, reconstructing lost evidence, the full 10-document evidence guide, the endorsement criteria, and the pain points hub.
Last updated: 6 July 2026. Facts verified against GOV.UK on 6 July 2026.