Open Source Project Name: Pick One and Check the Domain
Published 2026-10-05 · Updated 2026-11-05 · By Aaron Kempf
Startups Developer Domains Industry Planning Tutorial
Most open-source projects start as a repository with a working title. If the project catches on, that title becomes a brand: in conference talks, job adverts and other people's code. Choosing an open source project name with that future in mind takes an hour now and saves a painful rename later.
Why open-source naming is different
A company owns its name. An open-source project shares its name with everyone who forks it, packages it and writes about it. That has a few consequences:
- The name spreads before you've secured it. Blog posts and tutorials go up while you're still on a free hosting subdomain.
- Renames are expensive. Every dependency, import and tutorial uses the old name.
- Trademark questions come up eventually. Foundations that take on projects often ask who owns the name and the domain.
Where the name needs to be free
Check these before the domain:
- GitHub (or GitLab): the repository and, ideally, an organisation.
- Package registries for every language you'll support.
- A web search for the name plus "open source," to spot an existing project with the same name.
- Then the domain, on .org, .dev, .io or .com.
Choosing your open source project name
- Make it unique enough to search for. Dictionary words get lost in search results.
- Keep it short and lowercase-friendly. It will appear in import statements.
- Avoid a company's trademark, even as a tribute. "Something-for-BigBrand" can attract a polite but firm letter.
- Think about the logo. Animal and object names make projects easier to draw, which matters more than you'd expect for stickers and slides.
Which extension suits open source?
.org is the traditional home for non-commercial projects and foundations. .dev is popular for documentation. .io is common in the cloud-native world. A commercial company built around the project often uses the .com, so it's worth checking who holds that too.
Bulk Check lets you paste a list of candidate names and see every extension you care about in one run.
A worked example
A developer (invented for this example) has a small library for parsing log files, currently called "logparse." That's taken in two registries and impossible to search for. They list animal names connected to sifting or sorting, check them on GitHub and npm, and find two that are free in both. One is open on .dev and .org. They register both, move the docs to the .dev, and point the .org at it. The README now says the new name in its first line, with the old one mentioned once for search.
Protecting the name
- Register the domain with an account the project controls, not a personal one that might lapse.
- Write down who owns the domain in the repository, in a GOVERNANCE or MAINTAINERS file.
- If a foundation adopts the project, plan to transfer the domain to it.
For a broader look at extensions for technical audiences, see developer tool domain names.
Common mistakes
Keeping the working title too long. The longer a name is used, the harder it is to change.
Letting one maintainer hold the domain. If they leave, the project can lose its home.
Ignoring other registries. A Python port will need the same name on PyPI.
Related reading
- How to Pick a Side Project Domain Name in an Evening
- Product Launch Domain Checklist: Name to Go-Live
Frequently asked questions
Is .org still the right extension for open source?
It's a good default for community projects, but .dev and .io are equally common. Pick whichever is open and matches your audience.
Should I check trademarks for a hobby library?
A quick search is enough at first. If the project grows or a company forms around it, do a proper trademark search.