Formatting article coverFormatting article cover

How to Cite Software or a GitHub Repository in IEEE

An IEEE software reference gives the author, the software's title in italics, the date in parentheses, the repository or archive, the version, and an identifier such as a DOI (IEEE, 2025, p. 19). IEEE's basic format:

J. K. Author. Title of Software. (Date). Repository or Archive. (version or year). Publisher Name. Accessed: Date (when applicable). [Type of Medium]. Global Persistent Identifier. Available: site/path/file

Filled in for version 3.1.1 of pandas, the Python data analysis library, archived on Zenodo:

[1] The pandas development team. pandas-dev/pandas: Pandas. (Nov. 4, 2026). Zenodo. (v3.1.1). doi: 10.5281/zenodo.23955360.

In your sentence, the reference is its number in square brackets: "the data were cleaned with pandas [1]." IEEE sets the bracket on the line, inside the punctuation (IEEE, 2025, p. 4).

If the repository you used has no DOI, the next section is the one you need.

We checked the pandas release, its Zenodo records, and the paper cited below on November 17, 2026, and the pandas CITATION.cff file and the Requests release on November 18, 2026. Formats and examples are quoted from version 3.28.2025 of IEEE's reference guide.

How to cite a GitHub repository with no DOI

With no Zenodo record or other DOI, cite the GitHub release you used. Everything the entry needs is on GitHub:

  • Author: the authors the README names; if it names none, the person or organization that owns the repository (our advice).
  • Title: the software's name as the repository writes it.
  • Date: the date on the release page.
  • Version: the release's tag, such as v1.2.0.
  • URL: the address of the release page, which ends in /releases/tag/ and the tag.

Filled in for version 2.34.2 of Requests, the Python HTTP library, which has GitHub releases but no DOI:

[2] Python Software Foundation. Requests. (May 14, 2026). GitHub. (v2.34.2). Accessed: Nov. 18, 2026. [Online]. Available: https://github.com/psf/requests/releases/tag/v2.34.2

The README shows Kenneth Reitz's name only on a logo link and doesn't call anyone the author, so [2] names the organization that owns the repository.

The access date and "[Online]. Available:" come back, as in IEEE's Antcom and Ngspice examples: "Accessed: Abbrev. month and day, year," a period, then the URL, with no period at the end (IEEE, 2025, pp. 4, 22). Our advice: link the release, not the repository's front page, which changes with every commit.

IEEE's guide doesn't address a repository with no releases at all. Two things in it apply: the version slot reads "(version or year)," and a FORCE11 principle it reproduces asks software to be identified by "version numbers, revision numbers, or variants such as platforms" (IEEE, 2025, p. 19). Our reading: on GitHub, a commit is the revision, so give the access date and link the commit you ran.

How to format each part of an IEEE software reference

IEEE says it follows the FORCE11 Software Citation Principles and lists the details to give for each use of software. For software used in a paper, the list is "author(s), software name, location/repository, version number, release date, unique identifier" (IEEE, 2025, pp. 18-19). The guide's three examples, with the titles in italics as printed (IEEE, 2025, p. 20):

Antenna Products. (2011). Antcom. Accessed: January 11, 2019. [Online]. Available: https://www.antcom.com/products D. W. Arning et al. Mixed Mode–Mixed Level Circuit Simulator. (2011). Ngspice. Accessed: Jan. 11, 2019. [Online]. Available: http://ngspice.sourceforge.net MSDN Library Visual Studio 6.0. (2001). Microsoft.

How entry [1] fills each slot ("ours" marks where the examples leave the choice open):

PartWhat IEEE's format and examples showIn entry [1]
AuthorA person: initials and surname, as in the Ngspice example. A team or organization: its name in full, as IEEE writes Bureau of Meteorology and Doane Academy in other formats (IEEE, 2025, pp. 4, 14, 18)The pandas development team.
TitleIn italics, then a periodpandas-dev/pandas: Pandas.
DateIn parentheses. All three examples give the year only. Ours: the full release date, since the list above asks for the release date(Nov. 4, 2026).
Repository or archiveOne source after the date: Antcom, Ngspice, Microsoft. Ours: Zenodo is also the publisher, so it appears onceZenodo.
Version"(version or year)"(v3.1.1).
Access date and [Type of Medium]"When applicable"; in the examples, [Online] comes before "Available:" and a URL. Ours: [1] has no URL, so both are left outNone
Identifier"Global Persistent Identifier." Ours: the "doi:" label IEEE uses in its other formats. With no URL after it, the entry ends with a period (IEEE, 2025, p. 4)doi: 10.5281/zenodo.23955360.

The title, author, and version are copied from the Zenodo record for v3.1.1. The pandas citation page also says to use "The pandas development team" in place of the full author list (pandas, n.d.).

What GitHub's "Cite this repository" button gives you

When a repository has a CITATION.cff file, GitHub adds a "Cite this repository" link to the right sidebar of the repository page. GitHub's documentation: "We currently support APA and BibTeX file formats" (GitHub, n.d.-a). IEEE isn't one of them, so you build the IEEE entry from the file's details.

The pandas file gives the software's title and author, and a DOI:

title: 'pandas-dev/pandas: Pandas' doi: 10.5281/zenodo.3509134

It has no version and no release date; take both from the release you used. The file also lists Wes McKinney's 2010 paper, but among its references, not as its preferred citation, so "Cite this repository" gives you the software. A project that wants "the GitHub citation information to link to another resource such as a research article" can name a paper as its preferred citation instead (GitHub, n.d.-a). If the title the button gives you is a paper's, cite that paper as in the last section below, and still write the software entry from the release.

Which DOI to use: the release you ran

The DOI in the pandas file is not the one in entry [1]. Zenodo gives a record two kinds of DOI: one "representing the specific version of your record" and one "representing all of the versions of your record" (Zenodo, 2026). The file's DOI, 10.5281/zenodo.3509134, is the all-versions DOI: on November 17, 2026, it opened the record for v3.1.1, the latest release at the time. The pandas citation page uses it with the version "latest" and asks you to "find us on Zenodo and replace with the citation for the version you are using" (pandas, n.d.).

IEEE asks for the same: a FORCE11 principle in its guide wants "the specific version of software that was used" (IEEE, 2025, p. 19). Once a repository is linked, "Zenodo archives your repository and issues a new DOI each time you create a new GitHub release" (GitHub, n.d.-b).

First find out which version you ran. Our advice: ask the library (pandas.__version__ in Python) or your package manager (pip show pandas, conda list pandas), or read your environment file. Then open the project's Zenodo record, go to that version, and copy the DOI and date shown for it.

When the project asks you to cite a paper too

Some projects ask for a paper as well as the software. The pandas page asks for "citations to the published software and the following paper": Wes McKinney's 2010 conference paper (pandas, n.d.). That paper is a regular IEEE conference reference, checked against its Crossref record:

[3] W. McKinney, "Data structures for statistical computing in Python," in Proc. 9th Python Sci. Conf., 2010, pp. 56-61, doi: 10.25080/Majora-92bf1922-00a.

Proceedings becomes Proc., Science becomes Sci., and Conference becomes Conf. (IEEE, 2025, pp. 7, 27). In the text, cite both: "pandas [1], [3]."

Check the version, then the papers

Before you submit, open each software DOI or URL in your list and check that the version and date match the release you ran.

Papers like [3] can be checked against their published records. In PerfectRefs, you paste your reference list; you don't upload the paper. The Existence check looks up each reference in Crossref, OpenAlex, and other scholarly databases and flags any it can't find. It comes with a free daily allowance. The Style check compares authors, title, journal, year, volume, issue, pages, and DOI field by field with the database record, shows the record's values with a link to the source, and lets you accept a fix with one click. It uses premium credits (2 per reference), and new accounts get 10 premium credits. IEEE is one of the styles you can pick, and journal articles and books that match a record can then be reformatted in IEEE style and exported. A software release usually has no such record, and neither check compares version numbers, so the version, date, and DOI in your software entries are yours to check against the format above.

FAQ

Is the software title italicized in IEEE?

Yes. The title is italic in IEEE's software template and in all three of its examples (IEEE, 2025, pp. 19-20).

Does IEEE use a [Source code] or [Computer software] label?

Not in its software section. The template has a "[Type of Medium]" slot, and the two examples that fill it write [Online] (IEEE, 2025, pp. 19-20). [Computer software] is APA's label; see how to cite software in APA 7.

How do I cite an R package in IEEE?

The software format above works. IEEE's guide also has an R package among its Report Online examples: "R. J. Hijmans and J. van Etten, "Raster: Geographic analysis and modeling with raster data," R Package Version 2.0-12, Jan. 12, 2012," followed by "[Online]. Available:" and the CRAN URL (IEEE, 2025, p. 18). Our advice: pick one of the two formats and use it for every package in your list.

Original article by PerfectRefs. To republish it, credit PerfectRefs and link to this page. Do not edit it or use it commercially.