How it works
How it works
A Check, a review, and, if the Name is Taken, a round of Suggestions. Here is the whole path.
- Step 1
Type a Name
Enter a Name and press Enter or Check. It is validated against the Name validation rules before any Registry is asked.
- Step 2
Review the Registry results
Each Registry shows Available, Taken (with what it reports), Error or Rate limited.
- Step 3
Ask for Suggestions
If the Name is Taken anywhere, choose a Provider and select Suggest alternatives.
- Step 4
Compare re-checked Suggestions
Each valid Suggestion arrives with its own Registry status on all five Registries.
Under the hood
The browser talks only to the app’s own server routes: POST /api/check, POST /api/suggest and GET /api/providers. Every Registry and Provider call happens on the server.
A Re-check of Suggestions asks npm, Homebrew and PyPI once per Suggestion, but GitHub once for all of them, with a single OR query, to stay within GitHub’s search rate limit.
Registry results are cached in memory for 5 minutes (up to 1,000 entries), so checking the same Name again does not repeat the lookups.
Name it once, check it everywhere
Run Application Namer yourself: Registry checks work with no configuration, and one Provider key turns on Suggestions.