Evidence Building
Using Open-Source Contribution Records as O-1A Evidence: GitHub Stars, Fork Counts, and Downstream Citations
Software engineers and researchers whose most significant work lives in public repositories face a translation problem for O-1A petitions. This guide explains how to convert GitHub stars, downstream package citations, and upstream commits into evidence that satisfies the original contributions criterion.
The original contributions criterion and open-source evidence
The original contributions criterion under 8 C.F.R. § 214.2(o)(3)(iv)(A)(4) requires evidence that the petitioner has made original scientific, scholarly, or business-related contributions of major significance in the field. For software engineers, machine learning researchers, computational scientists, and open-source infrastructure developers, the most distinctive work often lives in public repositories rather than in peer-reviewed journals. A repository with substantial adoption metrics — thousands of stars, hundreds of downstream packages importing it, active fork communities — can represent a contribution of major significance. The challenge is presenting this evidence in a format that USCIS adjudicators, who are not trained in software development culture, can evaluate against the regulatory standard.
USCIS adjudicators reviewing original contributions evidence apply a two-part test: the contribution must be original and it must be of major significance — widely recognized and impactful within the field. Open-source contributions can satisfy both prongs when documented correctly, but the documentation burden is higher than for a peer-reviewed article with a documented citation count. An adjudicator may not understand what GitHub stars signify, why being listed in a package's dependency graph matters, or how an upstream commit to a widely used foundation library reflects on the contributor's standing in the field. The petition attorney must build this bridge explicitly in the supporting brief rather than assuming the metrics will speak for themselves.
This article covers how to construct an original contributions exhibit around open-source records. The approach applies primarily to O-1A petitions for software engineers, data scientists, computational researchers, and open-source infrastructure developers. The same evidence framework can support an original contributions narrative in cases where the petitioner also has traditional scholarly publications, but the article focuses on scenarios where open-source records are the primary contribution evidence. The general principles apply when other open-source platforms — GitLab, npm, PyPI, Hugging Face, or CRAN — serve as the primary repository hosting environment rather than GitHub.
What the regulation requires for original contributions of major significance
The regulatory text at 8 C.F.R. § 214.2(o)(3)(iv)(A)(4) describes original scientific, scholarly, or business-related contributions of major significance in the field as one of the eight O-1A criteria. The USCIS Policy Manual elaborates that the contribution must have significantly impacted the field. This is a higher bar than novel or useful — the question is whether the contribution changed how practitioners work, shifted methodological norms, seeded other researchers' work, or was adopted at a scale that signals broad recognition of the contribution's value. A repository with substantial adoption may clear this bar; a repository with a clever implementation and modest adoption typically will not, regardless of the technical quality of the underlying work.
The Policy Manual also notes that expert letters are important for explaining why a contribution is significant to those outside the field. This is especially true for open-source evidence, where the adjudicator cannot evaluate significance from the metrics alone. An expert letter describing why a specific machine learning library became the standard toolkit for a class of computer vision problems, and how that adoption level compares to comparable tools in the field, is more persuasive than a screenshot of star counts. The expert should have credentials establishing familiarity with the field and should speak to the contribution's impact on other practitioners rather than simply praising its technical quality or implementation elegance.
USCIS has not issued a memo specifically addressing open-source software contributions as O-1A evidence, but the AAO has sustained petitions in cases where software tools were documented with adoption evidence and expert support. The key doctrinal point is that original contribution of major significance is a field-relative standard. A project with 20,000 GitHub stars in a field where the most widely used tool has 100,000 stars may be highly significant; the same star count in a domain where cutting-edge research tools typically attract only 500 stars would represent extraordinary reach. Evidence of field context — what comparable tools look like, how the petitioner's repository compares to them — is essential for placing adoption metrics in perspective.
Evidence that routinely satisfies original contributions through open-source records
Downstream adoption records are among the strongest open-source evidence a petitioner can submit. When a package is listed as a direct dependency in hundreds of other published packages on PyPI, npm, CRAN, or the Hugging Face model hub, it demonstrates that independent practitioners found the work valuable enough to incorporate as a foundation for their own projects. An exhibit showing the petitioner's package as a dependency in hundreds of distinct projects — including named projects at established organizations or well-known research groups — is concrete evidence of adoption. The exhibit should include a brief explainer connecting downstream dependency counts to standard scholarly citation practice: practitioners treating a package as a dependency are analogous to scholars citing a paper as prior work.
Upstream commits to widely adopted foundation libraries are a second strong category of evidence. A petitioner who contributed a significant algorithmic improvement to NumPy, SciPy, PyTorch, TensorFlow, scikit-learn, or an analogous infrastructure project can document this through commit history and the project's changelog or release notes. If the contribution resolved a named issue, appeared in a release announcement, or prompted discussion among core maintainers whose expertise is documented, these records are part of the exhibit. An expert letter from a core maintainer or senior contributor to the foundation project — explaining what the petitioner's contribution improved and how it affected downstream users — is valuable supporting evidence establishing major significance.
Public recognition of the contribution by credible technical voices is a third strong category. This includes: posts by the project in official blogs, newsletters, or conference proceedings acknowledging a contribution; references to the repository in peer-reviewed papers by authors not associated with the petitioner; conference presentations where the project was cited as the methodology used; and industry adoption announcements where named companies disclosed use of the package in their production systems. Anything that shows practitioners outside the petitioner's own organization or research group independently recognized the contribution's value strengthens the major significance showing. The key is independence: recognition from people with no prior relationship to the petitioner carries more weight than internal praise.
Evidence USCIS regularly discounts from open-source portfolios
Raw GitHub star counts alone are insufficient to meet the original contributions standard without corroborating evidence of field significance. Stars are easy to accumulate through marketing and social sharing, and a repository with many stars may be a popular tutorial, a useful utility, or a notable demonstration project rather than a contribution of major significance. Adjudicators who receive a screenshot of a star count with no expert context will not know how to interpret it against the regulatory standard. The star count belongs in the exhibit as one data point within a larger evidence package rather than as the primary showing; on its own it proves the project attracted attention, not that it had significant impact.
Self-authored blog posts or social media posts praising the project do not satisfy the expert recognition requirement. The petition must show that others in the field recognized the contribution's significance, not that the petitioner described it as significant. Similarly, engagement metrics — Twitter followers, LinkedIn post likes, Reddit upvotes — are generally too informal and volatile to carry weight in a USCIS adjudication. Evidence of commercial use by recognized companies is stronger than any social engagement metric, and a letter from a named engineering team explaining how they incorporated the package into their production infrastructure is more persuasive than a comment thread, regardless of how many community members participated in that thread.
Contributions to a project the petitioner started themselves require careful framing. A petitioner who founded a widely adopted project is presenting evidence of their own original contribution, which is precisely the point — but the risk is that the adjudicator treats the petition as asking them to accept the petitioner's self-assessment of their work's importance. The antidote is third-party adoption records and external expert letters establishing that adoption and recognition came from independent actors who evaluated the work on its merits. The petition should demonstrate that the community's embrace of the project was driven by the work's quality and utility, not by the petitioner's own promotional efforts.
How to present borderline open-source evidence
A petitioner with a moderately adopted project — used in several recognized research groups but not yet widely adopted across the full field — can still satisfy the original contributions criterion if the framing establishes that the contribution represents a meaningful advance on prior methods in a specialized subfield. Niche contributions can qualify when the field context is properly explained. An expert letter should describe what the state of the art was before the petitioner's contribution, what specifically the contribution improved, and which practitioners subsequently adopted or cited the work. A focused subfield with a small number of practitioners has a lower adoption threshold than a general-purpose tool with millions of potential users, and the comparison baseline should reflect that difference.
Where the petitioner has a combination of open-source contributions and traditional scholarly publications, the petition strategy should present them as a coherent body of work rather than running two separate original contributions arguments. If the petitioner published a paper describing a method and then released an open-source implementation that achieved significant adoption, both pieces of evidence speak to the same underlying contribution. The paper establishes novelty and situates the work in the scholarly literature; the adoption records establish major significance in practice. This combination is typically more persuasive than either piece of evidence standing alone, and the petition brief should explicitly connect the two.
Timing matters for original contributions evidence. If the petitioner's most significant contribution was released several years before the filing date, the petition should address whether the work continues to be used or has been superseded by newer approaches. A package that was once widely used but has been deprecated or replaced by superior tools raises questions about sustained impact. The exhibit should show that the project remains maintained and adopted, or explain why the historical contribution was of major significance at the time it was made, even if subsequent developments have moved the field forward. USCIS evaluates the petition at the time of filing, so contemporary relevance matters.
Building and auditing your open-source evidence file
An open-source contributions exhibit should include: a technical summary of the project or projects written for a non-technical reader — explaining what problem the work solves, how it differs from prior approaches, and who uses it — along with quantified adoption metrics with timestamps, a curated list of named downstream users with evidence connecting each named user to the project, and at least two expert letters that address the significance question directly. The technical summary is often the most important document in the exhibit because it determines whether the adjudicator understands the contribution well enough to evaluate the adoption records correctly.
Before filing, run the exhibit through a plain-language test. Hand the technical summary to someone who does not work in software development and ask whether they understand what problem the project solves and why it matters. The USCIS officer reviewing the petition will have a similar vantage point. If the summary relies on unexplained technical terminology, revise it. The same test applies to the adoption metrics — if the adjudicator cannot tell whether 5,000 stars represents a lot or a little for this type of project without additional context, that context should appear in the exhibit or the petition brief.
A common audit failure is mismatching the petitioner's account identity across exhibits. If the petitioner's GitHub username changed, if contributions were made under an organization account rather than a personal account, or if some work was done under a prior employer's account, the exhibit must explicitly link all relevant accounts to the petitioner. USCIS has declined petitions where adoption evidence was associated with a repository whose connection to the petitioner was not clearly documented. Include contribution graphs, commit author records, and, where necessary, a declaration from the petitioner explaining the account history and establishing that the contributions documented in the exhibit are attributable to the petitioner personally.
What we typically gather for this kind of case
| Document | Where to source | Why it matters |
|---|---|---|
| Peer-reviewed publications | Web of Science / Scopus exports | Anchors original-contributions and authorship criteria |
| Citation analysis | Google Scholar profile + ESI top-1% data | Quantifies major significance in the field |
| Salary benchmark | BLS OEWS for SOC code + locality | Documents high-salary criterion at 90th-percentile or above |
| Critical-role letters | Direct supervisor + program director | Establishes role's importance, not just title |
What we see go wrong, again and again
- 01Treating extraordinary ability as a credentials checklist rather than a story of field-wide impact.
- 02Submitting bibliometric data (h-index, citation counts) without explaining what makes those numbers high relative to peers in the same sub-field.
- 03Relying on letters from collaborators or co-authors rather than independent experts who can speak to influence.
See if you qualify
Lando reviews your background against the O-1 visa criteria and tells you honestly where you stand. Free, no commitment.