USCIS Policy
How USCIS Evaluates Contributions to Open-Source Scientific Software as O-1A Original Contributions
USCIS evaluates open-source scientific software under the original contributions criterion, but raw download counts and GitHub metrics rarely carry the argument alone. Understanding what adoption evidence actually moves adjudicators — and how to present borderline software contributions — determines whether the criterion is met or an RFE follows.
The original contributions criterion and where open-source software fits
The original contributions criterion at 8 C.F.R. § 214.2(o)(3)(ii)(A)(5) requires evidence that the alien has made original scientific, scholarly, or business-related contributions of major significance in the field. The phrase "major significance" is the operative standard, and the USCIS Policy Manual instructs adjudicators to evaluate whether the contributions have influenced the field in a demonstrable way — not merely whether the contribution was novel or technically sophisticated. Open-source scientific software presents a recurring documentation challenge because the contribution itself is often unambiguous in terms of originality, but the evidence of major significance must be assembled from sources that do not always map neatly onto the petition exhibits adjudicators are most familiar with.
Software development for scientific research has become a core activity in fields ranging from computational biology and astrophysics to climate modeling and materials science. Researchers who build and release tools that enable other scientists to process, analyze, or visualize data are doing scientific work with direct consequences for how the field advances. The USCIS Policy Manual and AAO non-precedent decisions have acknowledged that contributions to scientific software can qualify under the original contributions criterion, but both make clear that significance must be demonstrated through concrete evidence of adoption and impact — not inferred from the technical complexity of the tool or the effort required to build it.
The practical challenge for petitioners is that software adoption is measured differently than scientific authorship. A paper's significance is partially captured by a citation count in a standard academic database. A software tool's significance may be reflected in GitHub metrics, in citations to the primary methods paper, in adoption by federal agencies or major research programs, or in testimonial evidence from researchers who use it. Because these metrics are less standardized than citation counts, the petition must work harder to contextualize them — explaining what each metric means in the specific research community and why it indicates major significance rather than ordinary professional usefulness.
What the regulation requires
The regulation does not define "major significance," but the USCIS Policy Manual specifies that contributions must have influenced the field beyond the petitioner's immediate collaborators. This distinguishes extraordinary ability from ordinary professional competence: most researchers produce work that is useful to their immediate colleagues; the O-1A category is reserved for those whose work has had a broader impact. For a software tool, this typically means demonstrating that researchers outside the petitioner's home institution — ideally at multiple institutions and in multiple research groups — have adopted and relied on the tool for their own scientific work. Adoption by a single major research center is weaker evidence than adoption by a diverse set of independent institutions.
The major significance standard also requires distinguishing the petitioner's contribution from incremental improvements to existing tools. Many software projects in research settings involve extending or modifying an existing platform — wrapping an existing algorithm, adding a new file format to a parser, or providing a more user-friendly interface to a well-established tool. These contributions may be valuable, but they are not original contributions of major significance unless the petitioner can show that the modification was non-obvious, filled a genuine gap in the field, and was adopted by other researchers specifically because of the petitioner's innovation rather than because of the underlying tool's existing reputation.
The AAO has not published a precedent decision specifically addressing open-source scientific software, but several non-precedent decisions involving software contributions suggest that the AAO applies the same totality-of-the-evidence standard it uses for other criterion types. A petitioner whose software tool is widely cited, adopted by major research programs, and supported by expert letters from prominent researchers in the field is likely to satisfy the criterion even if no single indicator is overwhelming on its own. Conversely, a petitioner who presents only download counts or GitHub stars without contextualizing them against field norms is unlikely to clear the major significance hurdle without additional supporting evidence.
Evidence that routinely satisfies the criterion
Citations to the primary methods paper for the software tool are the strongest single indicator of major significance, because they appear in a standardized, independently-verifiable database and demonstrate that other researchers have incorporated the tool into their scientific workflow in a way that required formal acknowledgment. A software tool with several hundred citations in peer-reviewed literature — documented by a Web of Science or Google Scholar citation report — typically satisfies the criterion when the expert letters explain what those citations represent in the context of the field. For tools with citation counts in the thousands, the citation record alone may be sufficient absent extraordinary contrary evidence.
Adoption by federal research programs or major research consortia provides a particularly strong form of evidence because it reflects an institutional decision to build scientific infrastructure on the petitioner's tool. A software package incorporated into a data processing pipeline for an NIH-funded consortium, an NSF MREFC facility, or a DOE national laboratory research program has been evaluated and selected by researchers working at the highest institutional levels. Documentation of this adoption should include letters or official statements from the program, the specific pipeline documentation naming the tool, and an explanation of why the program selected this tool over alternatives — showing that the selection reflected deliberate scientific judgment.
Publication of the software tool in a recognized academic journal — the Journal of Open Source Software, Bioinformatics, the Journal of Statistical Software, or SoftwareX, depending on the field — establishes scientific peer review of the tool itself, separate from any papers that use the tool. The Journal of Open Source Software in particular conducts explicit peer review of open-source research software through a structured editorial process, and publication there documents that the tool met peer-reviewed standards of documentation, functionality, and scientific utility. An exhibit combining the publication, its citation count, and a GitHub adoption metrics summary presents a well-rounded case under the original contributions criterion.
Evidence USCIS regularly discounts
Raw download counts and GitHub star counts presented without contextual explanation are among the weakest forms of evidence for the original contributions criterion. Downloads can reflect attempted rather than successful adoption, and GitHub stars are closer to bookmarks than to active use in scientific work. USCIS adjudicators reviewing petitions that lead with these metrics without explanation typically see them as thin evidence of significance rather than strong indicators, particularly when the petition provides no basis for understanding what level of downloads or stars would be meaningful relative to other tools in the same field. Presenting these metrics without comparison to field norms invites a finding that the contribution's significance is undemonstrated.
Self-reported usage statistics — claims that the petitioner's tool has been used by hundreds of research groups, based on user registrations, mailing list subscriptions, or internal download tracking — carry limited weight because they are not independently verifiable. USCIS adjudicators are trained to evaluate objective evidence rather than the petitioner's own characterizations of significance. A better approach is to document third-party verification of usage: published papers that acknowledge using the tool, letters from researchers at independent institutions who can confirm their adoption, or package repository download statistics from Bioconductor, PyPI, or CRAN showing institutional download patterns where available.
Minor contributions to existing major projects present a different documentation challenge. A researcher who has submitted code patches to a widely-used tool cannot claim that tool's entire impact as evidence of their original contribution. USCIS will look at whether the petitioner's specific contribution was itself of major significance — whether it addressed a problem that was beyond what others in the project were doing, whether it was adopted by the project's core maintainers as a meaningful advance, and whether the petitioner can document recognition from the broader project community for the specific contribution rather than for participation in the project generally.
How to present borderline evidence
When the software tool has a solid but not overwhelming citation record — say, in the fifty-to-two-hundred-citation range — the petition can strengthen the case by aggregating multiple weaker indicators into a coherent pattern. A tool with 150 citations, adoption by one major federal research program, a Journal of Open Source Software publication, and an expert letter from a prominent researcher who describes it as the standard approach for a particular analysis task presents a stronger package than any single element would alone. The supporting brief should synthesize these elements explicitly, making the inferential chain clear: adoption led to citations, citations led to further adoption, and the aggregate pattern demonstrates that the contribution influenced the field.
Expert opinion letters play a critical role in bridging the gap between metrics and significance. A letter from a researcher who did not collaborate with the petitioner but has used the software tool in their own published research can speak directly to the tool's scientific value in a way that the petitioner's own narrative cannot. The letter should explain what specific scientific problem the tool solves, why the petitioner's approach was non-obvious or superior to alternatives, what the field would have had to do differently without this tool, and what the expert's assessment of the tool's standing is among practitioners in the field. Generic praise of the petitioner's technical skill adds little; specific technical endorsement of the contribution adds substantially.
If the software tool has been independently reviewed or recommended in the scientific community — included in a comparative review article, recommended in a methods tutorial published in a high-profile journal, or evaluated in another researcher's grant application — that third-party endorsement provides evidence of significance distinct from direct adoption. A methods comparison article in Nature Methods or Bioinformatics that evaluates the petitioner's tool alongside competing tools and finds it competitive or superior establishes both that the tool was considered significant enough to warrant independent evaluation and that it met the scientific standards such evaluations apply.
Building and auditing your file
A complete original contributions exhibit for a software-focused researcher typically includes: a citation report for the software's primary methods paper from Web of Science or Google Scholar; a list of selected citing papers annotated to identify the research groups and institutions that adopted the tool; documentation of any federal program adoption with letters from program staff where obtainable; evidence of peer review of the software itself through a recognized journal; package-repository download statistics with a brief contextual explanation; and two or three expert opinion letters from researchers outside the petitioner's institution who can speak to the tool's significance in the field.
The supporting brief should explain the original contributions criterion and then map the petitioner's evidence to each element of the major significance standard: novelty, adoption, and impact. Petitioners who are strong on novelty but weaker on adoption should acknowledge the gap and explain why the adoption evidence they have is nonetheless adequate — for example, because the tool is specialized enough that adoption by a handful of leading research groups constitutes a dominant position within the relevant subfield. Adjudicators evaluating contributions in highly specialized research areas may not independently know that ten citations in a niche field represents a larger fraction of the relevant community than five hundred citations in a broader one.
If a request for evidence challenges the original contributions exhibit, the response should add expert letters if none were in the initial filing, obtain adoption documentation from any research programs that use the tool, and locate any published comparisons or reviews that evaluate the tool's performance against alternatives. An RFE challenging the original contributions criterion often reflects an adjudicator who did not understand the significance metrics provided — the response should treat the RFE as an opportunity to provide additional context rather than simply resubmitting the same evidence with a cover letter arguing it was sufficient the first time.
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.