Features
Features
Everything Application Namer does, one page per feature, with the numbers that apply.
- 01
Five Registries in one Check
npm, Homebrew Formulae, Homebrew Cask, PyPI and GitHub are asked in parallel; you get one Registry result per Registry.
- 02
Four Registry statuses
Every Registry result is Available, Taken, Error or Rate limited, so “unknown” is never shown as “free”.
- 03
Suggestions from a Provider
When a Name is Taken, pick a Provider and get 8 Suggestions: Claude API, OpenAI API, or Claude, Codex or Copilot through an MCP bridge.
- 04
Every Suggestion re-checked
Each valid Suggestion gets its own Re-check on all five Registries before you see it, with GitHub asked once for the whole batch.
- 05
Name validation rules
One set of rules in the browser and on the server: lowercase letters, digits, -, _ and ., at most 214 characters, not scoped.
- 06
In-memory result cache
Registry results are kept for 5 minutes, up to 1,000 entries, so checking the same Name again does not repeat the lookups.
- 07
Graceful degradation
A Registry or Provider that fails shows its own Error; every other result still appears.
- 08
Keys stay on the server
Every Registry and Provider call runs in the app’s own server routes, so Provider keys and the GitHub token never reach the browser.
Name it once, check it everywhere
Run Application Namer yourself: Registry checks work with no configuration, and one Provider key turns on Suggestions.