Naming a project sounds simple until you actually have to do it. You want something memorable, something that tells people what the product does, and something that won't get you into legal trouble. Finding all three in one name is harder than it sounds.
Here's how I ended up with DruScan.
The Drupal Trademark Problem
My first instinct was to use something obvious. Drupal Audit. Drupal Monitor. Drupal Health. Names that immediately tell you what the product is about.
But there's a problem. Drupal is a registered trademark owned by the Drupal Association. Using the full word "Drupal" in a commercial domain or product name is risky. The community has every right to protect their trademark, and I've seen cases where domains were challenged and taken down.
I didn't want to build a product, invest time and money into it, and then receive a cease and desist letter asking me to change everything. So any name containing the full word "Drupal" was out.
The DruForge Mistake
I liked the idea of a forge. A place where tools are created and refined. It felt like a good metaphor for what I'm building: a set of tools to help developers polish and improve their Drupal projects.
So I bought the domain DruForge without thinking too much about it. It sounded good, the domain was available, done.
Then I made the search I should have made before buying. There's already a project in the Drupal community with a very similar name. It's actively maintained and has some visibility. Using DruForge would create confusion, and the last thing I need is people mixing up my product with someone else's project.
I still own the domain, but I won't use it. Lesson learned: always search before you buy.
Finding DruScan
After discarding DruForge, I started looking for alternatives. I wanted something short, easy to remember, and that hinted at what the product does.
DruScan felt right. "Dru" as a shorthand for Drupal, "Scan" because the product scans your site for issues. Simple and descriptive.
When I searched for it, I only found an old repository from about 10 years ago. It looked completely abandoned, with barely any code, and seemed to have a similar intention to my old bash scripts: simple checks for specific things. But it was clearly a dead project that never went anywhere.
The domain was available. The namespace on Drupal.org was free. I couldn't find any active project or company using the name. So I registered the domain and started building.
The Timing Problem
A few weeks after I registered the domain in December 2025, I discovered something annoying. Just days before I registered my domain, a company in the Drupal community had created a Git repository with the exact same name. Their tool is meant to run against repositories, similar to what my original bash scripts did before I converted everything to a Drupal module.
Great timing, right?
I spent some time thinking about whether I should change the name. But honestly, I couldn't find anything better. Every alternative I considered either had trademark issues, was already taken, or just didn't feel right.
Why I Decided to Keep It
I considered using a subdomain under my personal freelance domain, but that felt wrong. I don't want to tie this product to my freelance brand. If DruScan succeeds, it should stand on its own. If it fails, I don't want it dragging down my reputation as a freelance developer.
So I looked at the situation more carefully. The other DruScan project is open source, designed to run locally with repository access. They don't have the domain. They don't have the namespace registered on Drupal.org. And they clearly didn't mind using a name that was already attached to that abandoned 10-year-old repository.
If they weren't concerned about name overlap with an older project, I figured I shouldn't be too worried either. Especially since I have the domain and the official module namespace.
The products are also different enough. Theirs runs against repositories. Mine is a module you install on your Drupal site that connects to a centralized dashboard. Different approaches, different target users.
Sometimes Good Enough Is Good Enough
In the end, I kept the name because I like it and because changing it would mean starting over with branding, domains, and all the content I've already created. Perfect is the enemy of done, and I'd rather launch with a name that's good enough than spend another month searching for the perfect name that probably doesn't exist.
DruScan it is.