I used to agonize over naming my projects. First there's sweating over the repository name, then the repository name eventually leaks into the top-level module name. And the database. And the package.
Eventually I figured it out: Dumb. Project. Names.
Using machine vision to plot deforestation? Demeter.
Visualizing the political machinations of the French Revolution? Guillotine.
A new system reliability tool? Argon.
Just a short punchy word, that's all you need.
Yes, the name is still going to leak into the database name, the top-level imports, etc. Since we've separated the "project" name from the "marketing" name now though...who cares?
Then when you go live and make your landing page, you find a "front-facing" name that actually works.
You can also change project purpose mid-way and your top-level name won't be out of date.
This is just fun. It's whimsical, and we need harmless whimsy in software now more than ever.