mmodiqo/package-name-searchv1.1.2Public
Package name search
Checks candidate package names across npm, PyPI, and crates.io in parallel, then ranks names by likely availability without claiming publish guarantees.
Read the full description
Each registry is its own DAG step, so probes run concurrently, an unreachable registry degrades to labeled indeterminate rows instead of failing the play, and the ranking join shows exactly which registry said what.
Before you run it1 local tool
Everything here is checked on your machine when rote inspects the play. This page never learns what you have installed or which credentials you hold.
- ○python3local tool
Must be on your PATH. rote reports what it finds during inspect.
Inputs3, all optional
rote asks for these before running and shows the defaults it will use.
- Names
namesComma-separated candidate package names
optionalstringdefaultrote-example,rote-example-cliexamplemy-tool,my-tool-clicustom value allowed - Ecosystems
ecosystemsComma-separated registries; npm, pypi, and cargo are supported
optionalstringdefaultnpm,pypi,cargoexamplenpm,cargocustom value allowed - Max candidates
max_candidatesMaximum candidate names to check, from 1 through 50
optionalintegerdefault20example20custom value allowed
What it changes
No write operations are declared in this version's manifest.
Credentials remain in the recipient's local rote vault; this page and the publisher never receive them.
Runtime details
- rote CLIversion 0.62.0 or newer
- Servicesnone declared
- Digest
sha256:c2ba24d2f701df5258f020a2274e8c4bc47bea105c4b3d095e5816104eda7e71 - Archive size6556 bytes
- Published2026-08-17T23:58:03.368794+00:00
- Published withrote 0.66.1
Credential values and current readiness remain local. Opening this page never prompts for a credential, opens an authorization browser, or calls a service this play uses.
A play is a published, versioned automation package that runs on your own machine through rote, a free command-line tool. Opening this page installs nothing and runs nothing.