USCIS Policy
How USCIS Evaluates O-1A Original Contributions Evidence from Open-Source Software and Code Repository Contributions When There Are No Traditional Publications in 2026
USCIS applies the original contributions criterion skeptically to open-source software evidence when no traditional publications exist. This guide explains what adjudicators look for, what download metrics cannot show, and how to build a major significance argument from adoption records, academic citations, and technical expert declarations.
The original contributions criterion and the open-source challenge
The original contributions of major significance criterion, codified at 8 C.F.R. § 214.2(o)(3)(iii)(E), is the O-1A criterion that most frequently generates RFEs for petitioners in software engineering, data science, and technical research roles where the primary output of their work is code, software tools, or open-source infrastructure rather than peer-reviewed journal articles. The criterion requires evidence that the alien has made original scientific, scholarly, or business-related contributions of major significance in the field. For petitioners whose professional contributions exist primarily in code repositories, the petition must translate the technical significance of software contributions into the legal and administrative framework of the O-1A original contributions standard.
Open-source software contributions present a distinctive evidentiary challenge because the primary record of the contributions — GitHub commits, pull requests, package release histories, and repository stars — is technically verifiable but administratively unfamiliar to USCIS adjudicators. A petition that presents thousands of GitHub stars or millions of package downloads as proof of major significance without contextual explanation is unlikely to succeed. The petition must bridge the gap between the metrics of the open-source software ecosystem and the legal standard of major significance in the field, using expert evidence and industry adoption documentation to establish that the contributions have had a measurable effect beyond the immediate user base.
USCIS has addressed open-source contributions in the context of the O-1A original contributions criterion in a growing body of non-precedent AAO decisions, as well as in RFE notices that have established the agency's working framework for evaluating this evidence type. The consistent theme in USCIS guidance — both from the Policy Manual and from AAO reasoning — is that metrics of use and adoption, standing alone, do not establish major significance. The petition must demonstrate that the software contributions have had a measurable effect on the field: that practitioners in the relevant technical domain use the software in ways that have advanced the state of the art, solved problems that were previously unsolved, or enabled new categories of work.
What the regulation requires
The regulatory text requires original scientific, scholarly, or business-related contributions of major significance. For open-source software, USCIS and the AAO have interpreted major significance to require that the contribution has had a notable effect on the field beyond the immediate users of the software — that other researchers or practitioners have built on it, cited it, or recognized it as advancing the field. A software library downloaded millions of times for routine tasks does not establish major significance if it is one of many standard tools for the same purpose; a software library downloaded less frequently but recognized by leading researchers as solving a previously intractable problem may establish major significance even with a smaller adoption footprint.
The original component of the criterion requires that the petitioner's contribution can be distinguished from the work of others — that it represents the petitioner's own intellectual contribution rather than a straightforward implementation of a known algorithm or a fork of existing open-source code with minor modifications. The petition must identify the specific technical insight or innovation that makes the petitioner's contribution original, explain what the technical state of the field was before the contribution, and demonstrate how the contribution changed or advanced that state. Expert declarations from technical researchers or industry practitioners who can explain the novelty of the contribution in terms accessible to a non-specialist adjudicator are essential for this component.
For petitioners who have contributed substantially to major open-source projects but have not authored those projects — who have made significant pull request contributions to well-known repositories — the original contributions analysis must focus on the petitioner's specific contributions rather than the project as a whole. A contribution that fixed a critical bug enabling a major platform to scale, added a core feature that became widely used, or redesigned an architectural component in a way that substantially improved performance or capabilities may qualify as an original contribution even though the repository itself is the work of a large community. The petition must document the specific contribution and its impact with precision.
Evidence that routinely satisfies the criterion
Citations to open-source software in peer-reviewed academic publications are the strongest form of original contributions evidence for code-based work, because they establish that the academic research community has recognized the software as a scholarly contribution. A software library that has been cited in publications indexed in Google Scholar, ACM Digital Library, IEEE Xplore, or arXiv demonstrates that researchers in the field treat the software as a tool of scientific or technical significance. The petition should identify the citing publications, provide the publication context — journal ranking, conference tier, author affiliations — and note the specific use described in each citing paper, not merely the citation count but evidence of what the software enabled in each study.
Adoption by major technology companies, government agencies, or recognized research institutions provides field impact evidence that is functionally similar to citation evidence but operates in the industry rather than academic context. A letter from a senior technical leader at an organization that has deployed the petitioner's software in production — explaining what the software does, how it compares to alternatives, and why the organization selected it — establishes that recognized technical institutions treat the petitioner's software contributions as distinctive and valuable. Contributions to the Linux kernel, major Python libraries, CNCF-hosted projects, or other recognized infrastructure maintained by neutral technical governance organizations carry institutional credibility that reinforces the major significance claim.
Technical awards, recognitions, and competitive selections — such as serving on a program committee for NeurIPS, ICML, ICLR, or other top-tier technical conferences, receiving recognition from the Linux Foundation, the Apache Software Foundation, or the ACM for distinguished open-source contributions, or being invited to participate in Google Summer of Code as a mentor — demonstrate that recognized institutions in the technical field have treated the petitioner as a distinguished contributor. These recognitions can serve double duty in an O-1A petition, supporting both the original contributions criterion and the judging criterion for conference program committee service, or the recognition criterion for institutional awards.
Evidence USCIS regularly discounts
GitHub star counts and npm download statistics, presented without contextual explanation, consistently receive limited weight from USCIS adjudicators in the original contributions analysis. Adjudicators have appropriately noted that download metrics reflect popularity but not necessarily significance — a utility library downloaded as a dependency of another package may accumulate millions of downloads through automated build processes without representing a meaningful technical contribution to the field. The petition must go beyond quantitative metrics to explain the qualitative significance of the software and demonstrate that knowledgeable practitioners in the field treat the petitioner's contributions as distinctive rather than merely widely used.
Self-authored blog posts and personal documentation describing the technical significance of the petitioner's software contributions, while potentially useful for educational context within the petition, are not treated as independent evidence of major significance. USCIS adjudicators appropriately require that claims of significance be corroborated by sources independent of the petitioner who have the expertise to assess the technical claim. A GitHub repository's own README file, however well-written, is authored by the petitioner and cannot serve as independent corroboration that the software has major significance in the field — it establishes what the petitioner says about the software, not what the technical community has concluded.
High follower counts on developer communities such as X, LinkedIn, or Hacker News, without evidence connecting those followers to the field-level significance of the software contributions, are insufficient to satisfy the original contributions criterion. Social media presence in the developer community reflects visibility and communication skill, which may be appropriate evidence for a media or recognition criterion, but does not itself establish that the petitioner's software contributions have advanced the technical state of the art. The petition should avoid conflating the petitioner's reputation as a communicator in the developer community with evidence of the substantive field impact of the code contributions themselves.
Framing comparable evidence effectively
For a petitioner whose open-source contributions are genuinely significant but not widely cited in academic literature — perhaps because the software is primarily used in industry rather than academic research — the petition should build the major significance showing around industry adoption evidence rather than academic citations. A declaration from a chief technology officer, senior engineering manager, or distinguished technical fellow at a recognized technology company who can explain the specific technical problem the petitioner's software solves and why that solution represents a meaningful advance over prior alternatives is functionally equivalent to a citation in a peer-reviewed paper for purposes of establishing field impact in an industry-dominated technical domain.
Where the petitioner's contributions exist at the intersection of open-source software and academic research — as is increasingly common in machine learning, bioinformatics, climate modeling, and other fields where research software has become a central form of scientific output — the petition should document both the academic citation record and the industry adoption record to build a comprehensive picture of field impact. An open-source machine learning framework cited in papers at NeurIPS and also deployed by major companies provides evidence of major significance from two independent evaluating communities, strengthening the original contributions showing beyond what either record alone would establish.
For petitioners who have made foundational contributions to a project that has since been adopted broadly — contributing early architecture or core algorithms to a framework that now has a large community — the petition should document the nature of the early contribution with specificity: the commit history, the technical design documents, the architectural decision records, or the original RFC that proposed the design now embedded in the mature project. Attribution of foundational contributions in a large collaborative project is a common challenge, and the petition must present enough technical detail to allow an adjudicator to understand why the petitioner's specific contribution — and not merely the project's subsequent success — reflects the petitioner's individual original work.
Building and auditing the original contributions file
A complete original contributions criterion package for a software engineer or researcher without traditional publications should include: expert declarations from at least three technically qualified practitioners — ideally including both academic researchers and industry practitioners — who can explain the significance of the petitioner's specific contributions in terms of the problem solved, the prior state of the art, and the impact on the field; evidence of academic citation where it exists, with context about the citing publications; evidence of adoption by recognized institutions, with letters from deployment sites where possible; and technical recognition from industry or academic organizations in the relevant domain.
The petition brief should include a technical narrative explaining the petitioner's specific contributions in plain language accessible to a non-specialist adjudicator. This narrative should not assume that the adjudicator understands the technical field — it should begin with a brief description of the problem the software addresses, explain the prior approaches and their limitations, describe what the petitioner's contribution introduced that was new or better, and document the effects of that contribution on subsequent work in the field. The narrative should be written with the same care given to any other part of the petition brief, because it provides the interpretive frame through which the adjudicator evaluates all of the technical and expert evidence.
The petition team should audit the original contributions evidence with particular attention to whether the expert declarants are identifying the petitioner's specific contributions or the project's general importance. An expert declaration that praises the open-source ecosystem broadly — noting that the project has millions of users and is widely regarded as important — without specifically attributing field-advancing significance to the petitioner's individual contributions does not satisfy the criterion. Each declarant should be briefed to address the petitioner's personal contribution to the field — what the petitioner specifically built, designed, or discovered — rather than the success of any project or team with which the petitioner was affiliated.
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.