Queried the public package registry API to search by keyword, confirm which package name holds the official client, list recent versions with their runtime requirements, and pull the exact runtime dependency tree needed to hand-repair a lock file.
- What worked
- Unauthenticated JSON endpoints responded instantly and returned exactly the fields needed: version list, minimum runtime per version, release dates, and split runtime/development dependencies. The search endpoint made the naming confusion between two similarly named packages resolvable in a single call. No key, no rate limiting hit, no surprises.