npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@cradler/router-setup

v0.2.1

Published

One-command setup: point Claude Code, Codex, and Gemini CLI at Cradler Router.

Downloads

38

Readme

@cradler/router-setup

One command to point your coding agents at Cradler Router:

npx @cradler/router-setup sk-cr-your-key

Get a key at cradler.ai/dashboard/router, run the command, and every supported agent on your machine is configured — then the tool verifies your key against the Router with a live call.

What it configures

Always (these tools' own config locations, safe to create):

| Agent | File | What | |---|---|---| | Claude Code | ~/.claude/settings.json | env.ANTHROPIC_BASE_URL + env.ANTHROPIC_AUTH_TOKEN | | Codex | ~/.codex/config.toml | a [model_providers.cradler] block (wire_api = "responses"), switches model_provider | | Shell key | ~/.zshrc / ~/.bashrc | export CRADLER_ROUTER_KEY=… inside # >>> cradler-router >>> markers | | Gemini CLI | ~/.gemini/.env | GOOGLE_GEMINI_BASE_URL, GEMINI_API_KEY, GEMINI_API_KEY_AUTH_MECHANISM |

When detected on your machine:

| Agent | How | |---|---| | OpenClaw | ~/.openclaw/openclaw.json — cradler (OpenAI protocol) + cradler-claude (Anthropic protocol) providers | | ZCode | ZCODE_* exports in the same shell marker block | | Cherry Studio | opens the official cherrystudio:// one-click import (force with --cherry) | | DeepSeek Harness (dsh) | a cradler provider in $DSH_HOME/settings.yaml, keyed off CRADLER_ROUTER_KEY |

dsh custom providers accept the OpenAI protocols only, which is no longer a limit: /v1/chat/completions carries the whole catalog, so that one route reaches Claude and Gemini too. $DSH_HOME must already exist — we honor the env var, or ~/.dsh / ~/.deepseek-harness if present, and never create a home dsh has not made. A pre-existing llm-pi-ai: section we did not write is left alone and reported, so your own provider config is never clobbered.

UI-configured apps (their settings live inside the app, so no file to write safely): run with --guides to print paste-in values for Cursor, Trae, WorkBuddy/CodeBuddy, cc-switch.

  • Idempotent — run it again with a new key to rotate; only our markers/blocks are replaced.
  • Everything else in those files is left untouched.
  • To undo: remove the marker block from your shell profile and from $DSH_HOME/settings.yaml, the cradler* providers from ~/.codex/config.toml / ~/.openclaw/openclaw.json, and the two env entries from ~/.claude/settings.json.

Manual setup

Prefer to do it by hand? Every snippet is in the API docs.

License

MIT