Researchers can make software count as a research output by publishing it in recognized venues, archiving it with a persistent identifier, and documenting it thoroughly so others can cite and build upon it.
Publish in Software-Specific Journals
Several peer-reviewed journals now accept software papers that describe computational tools, algorithms, or research infrastructure. The Journal of Open Source Software (JOSS), SoftwareX, and the Journal of Statistical Software publish citable articles focused on research software. These publications provide DOIs and formal peer review, establishing your software as a legitimate scholarly contribution that appears in citation metrics.
Archive with Persistent Identifiers
Deposit your software in a recognized repository that issues persistent identifiers like DOIs. Zenodo, figshare, and the Software Heritage archive all provide long-term preservation and citeable DOIs. GitHub repositories alone don't count as formal research outputs because URLs can break and code can disappear—archiving ensures your work remains accessible and traceable. Include version numbers and release notes so others can reference specific iterations.
Document Thoroughly
Write comprehensive documentation that explains what your software does, how to install and use it, and what research problems it solves. Include a clear README file, user guides, and API documentation. Add a CITATION.cff file or similar citation metadata directly in your repository so users know exactly how to cite your work. This makes your software more discoverable and easier for others to acknowledge in their research.
Link to Publications
If your software supports a research paper, explicitly mention it in the publication and vice versa. Cross-reference the software DOI in your paper's data availability statement and cite the paper in your software documentation. This bidirectional linking strengthens the connection between your code and your broader research narrative.
Highlight in CVs and Grant Applications
List software outputs separately in your CV under a dedicated section for research software or digital scholarship. Include download statistics, citation counts, and community contributions as evidence of impact. Many funding agencies now recognize software as a valid research output—NSF's Biographical Sketch format explicitly allows software citations, and the UK's REF framework considers research software in impact assessments.
