Evidence Building
How to Document Software Library Authorship as O-1A Original Contributions Evidence in 2026
Software library authorship is underused as O-1A original contributions evidence. Download statistics, academic citation counts, and dependent repository data can establish major significance when presented with field context — but only when expert letters document the library's influence on research practice rather than its technical quality alone.
The original contributions criterion and how software fits within it
The original contributions of major significance criterion under 8 C.F.R. § 214.2(o)(3)(iv)(A)(5) requires evidence that the petitioner has made original scientific, scholarly, or business-related contributions of major significance in the field. For researchers and engineers who have authored open-source software libraries — tools that accelerate scientific computation, enable machine learning workflows, or provide infrastructure for an entire research community — the criterion offers a natural home for software-based achievements. The question is not whether software can qualify, but how to document the library's adoption, influence, and standing in a way that USCIS adjudicators can evaluate without technical expertise in the specific domain.
The USCIS Policy Manual does not categorically exclude software from the original contributions criterion, and practitioners have successfully submitted software libraries as original contribution evidence for petitioners in computational science, bioinformatics, artificial intelligence, and related fields since the criterion was first applied to technology-intensive roles. The AAO has affirmed that contributions to a field do not require the form of a peer-reviewed journal article — what matters is whether the contribution was original, was made in the petitioner's field, and was of major significance. A software library that solves a previously intractable problem, formalizes a new computational approach, or provides infrastructure that substantially advances a field's research capacity can satisfy all three requirements if the evidence supports those claims.
Software library authorship presents a documentation challenge distinct from traditional academic contributions. Publication metrics for journal articles — citation counts, journal impact factor, h-index — have direct analogues in the software world: download statistics, repository stars, dependent project counts, and citations to the library in academic literature. These metrics are meaningful, but they require context. A library with five thousand monthly downloads may be the most widely used tool in a niche scientific field or a modestly popular utility in a mass-market context; the raw number carries different evidentiary weight depending on field context. Expert letters must supply that context explicitly.
What the regulation requires for original contributions of major significance
The regulatory phrase of major significance is the interpretive crux of this criterion. The USCIS Policy Manual elaborates that contributions must have influenced the field in a substantial way and that evidence of widespread adoption is relevant to establishing major significance. For a software library, major significance is demonstrated through documented influence on the field's research practices: adoption by a significant number of independent research groups, citations in peer-reviewed literature, integration into downstream software used by the broader community, or recognition in field-specific reviews or surveys of the state of the technology.
Originality for software purposes means more than functional novelty. A library that reimplements a published algorithm is not original in the sense the criterion requires, even if the implementation is efficient or well-documented. Originality under the O-1A framework means the library introduced a new computational approach, formalized a previously informal technique in a way that made it tractable at scale, solved a problem the field had not previously solved computationally, or built infrastructure that enabled research not previously possible. Expert letters must describe what specific problem the library addressed, what the prior state of the art was, and how the library's approach differed from existing solutions in the field.
The major significance standard also carries a scope dimension: contributions must be significant in the petitioner's field, not merely in a narrow subcommunity. A library that is the standard tool for researchers in a specific subspecialty — such as a particular genomic sequencing analysis pipeline or a computational fluid dynamics solver — satisfies the standard if the petitioner documents that the subspecialty is a recognized and significant area of the broader field and that the library's adoption within that subspecialty reflects field-wide recognition. Expert letters from researchers outside the petitioner's immediate collaborator network are particularly valuable in establishing this broader reach of recognition.
Evidence that routinely satisfies the criterion for library authors
Download statistics from package repositories are the most readily available quantitative evidence. For Python libraries, PyPI download statistics are publicly accessible and can be presented with context about the repository's overall activity in the field. For R packages, CRAN download counts serve the same function. For compiled software distributed via release platforms, download counts document adoption scale. These statistics should be accompanied by an expert letter explaining what typical download volumes in the relevant subcommunity represent in terms of user adoption, because raw numbers convey no significance without field context that allows an adjudicator to assess whether the adoption level is extraordinary for the specific research area.
Citations to the library in peer-reviewed academic literature are the most direct evidence that the software has influenced research practice. When a software library is published alongside a journal article — in software-focused venues like the Journal of Open Source Software, the JMLR Machine Learning Open Source Software track, or Bioinformatics — the citation record of that software paper serves as the primary quantitative indicator of scholarly influence. Google Scholar citation counts for the software paper, combined with a representative list of citing papers demonstrating the range of research applications and the independence of the citing groups, provides a compelling exhibit that maps directly onto the USCIS standard for major significance.
Dependent repositories — repositories maintained by third parties that list the petitioner's library as a dependency — provide a measure of adoption distinct from download statistics or citations. Each dependent repository represents an independent research group or development team that has integrated the petitioner's software into their own work. For a library serving a research community, dependent repositories at recognized institutions — universities, national laboratories, industry research groups — are qualitatively strong evidence, particularly when accompanied by a letter from one of those groups' investigators confirming their reliance on the library for active research. An exhibit listing institutional affiliations of dependent repository owners, with a count of independent adopters, converts a repository metric into a concrete description of field-wide adoption.
Evidence USCIS regularly discounts in software contribution cases
Repository star counts are visible to adjudicators and may appear impressive numerically, but absent an expert letter explaining what such counts mean in the petitioner's specific field, they do not establish major significance. A library with fifty thousand stars in a mass-market web development context represents a very different level of field-wide recognition than five hundred stars in a computational biology niche, where five hundred may represent near-universal adoption by every active research group in the area. Without field context, adjudicators cannot assess significance, and the metric proves nothing standing alone — a point practitioners have learned through RFE responses that specifically request field benchmarks for quantitative metrics.
Self-citations do not demonstrate that others in the field have adopted or recognized the contribution. USCIS adjudicators applying the major significance standard look for adoption and recognition by independent third parties. A citation record dominated by the petitioner's own publications fails this requirement even if the total citation count appears substantial. The exhibit should clearly distinguish self-citations from independent citations, and the accompanying expert letter should confirm that cited papers represent independent research groups using the library for substantive research purposes, not merely referencing it in passing or citing it to acknowledge the software tool used in a routine data analysis workflow.
Expert letters that praise the library's quality or technical elegance without addressing its influence on the field are consistently insufficient. USCIS is not assessing code quality or technical skill — it is assessing whether the contribution has had major significance in the field. A letter that describes the library as well-designed or efficient without documenting specific research outcomes it enabled does not establish that the contribution meets the regulatory standard. Expert letters for software contributions should describe what research was made possible, or substantially easier, by the library, and should cite specific examples from the expert's own research experience or from published literature in the field.
Framing borderline contributions effectively
Many software library cases involve contributions that are strong qualitatively but thin quantitatively — the library is highly regarded in a niche field where the field itself is small. For these cases, the framing strategy is to establish the significance of the subspecialty first before documenting the library's position within it. An expert letter that describes the subspecialty's importance to a broader discipline — characterizing the number of active research groups, the volume of publications in top-tier venues, and the connection to significant applied problems — provides the contextual foundation that makes the library's adoption within that community meaningful to an adjudicator without domain expertise in the specific area.
Version history and release cadence provide evidence of sustained contribution that supplements a point-in-time adoption snapshot. A library that has been actively maintained and developed over several years, with regular releases responding to community needs and reported issues, demonstrates ongoing engagement with the field that distinguishes the petitioner's role from that of a one-time contributor. The petitioner should document the release history, the issues and pull requests that led to major versions, and any community governance role the petitioner holds in the project, such as serving as the primary maintainer or as a member of the project's steering committee or advisory board.
Integration into well-known downstream software ecosystems provides strong evidence of field-wide significance. If the petitioner's library is a component of a major framework or platform widely used in the field — incorporated into a broadly adopted machine learning ecosystem, a scientific computing stack, or a bioinformatics pipeline — that integration establishes that the library was evaluated and accepted by the maintainers of that ecosystem as meeting a sufficiently high bar of reliability and utility. Documentation of this integration, including the review process by which the library was incorporated, provides concrete evidence of recognition by the field's major infrastructure stakeholders that is qualitatively stronger than user-facing download statistics alone.
Building and auditing your software contributions file
A complete software contributions exhibit for an O-1A petition should include, at minimum: the software library itself with documentation of its public release date and version history; download statistics from the relevant package repository with annotation explaining field context; citations to any associated software paper in peer-reviewed literature, with a count of independent citations clearly distinguished from self-citations; a list of dependent repositories with institutional affiliations; at least two expert letters from independent researchers in the field who address the library's significance relative to the prior state of the art; and any formal recognitions such as inclusion in curated tool registries, feature coverage in field survey articles, or awards from professional organizations in the domain.
Before submitting, audit the exhibit for gaps that RFEs commonly address in software contribution cases. The most frequent issues are: insufficient documentation of the petitioner's individual role in a multi-contributor project, since the petition must establish that the petitioner made the original contribution and not merely participated in a team effort; absence of field context for quantitative metrics, since download counts must be explained relative to the field's scale and activity; and expert letters that address technical quality rather than field significance, which should be replaced with letters that document adoption and influence specifically. Addressing these issues before filing substantially reduces the risk of a request for evidence.
The software contributions exhibit is strongest when organized around the regulatory standard — original contribution of major significance — rather than around the petitioner's career narrative. Each piece of evidence should map explicitly onto one element of the standard: originality, which means what was new about the contribution as described by an independent expert; significance, which means adoption metrics with field context that allow the adjudicator to assess whether the contribution's reach is extraordinary; and major impact, which means testimony about specific research outcomes the library enabled. An exhibit organized this way gives the adjudicator a clear basis for applying the regulatory standard without inferring connections from an unstructured document collection.
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.