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

@unbyte/ccc

v0.0.2

Published

> a thin wrapper that launches `claude code` with named configuration profiles.

Readme

@unbyte/ccc

a thin wrapper that launches claude code with named configuration profiles.

Why

  • Named profiles for any combination of provider, model, thinking effort, env, and settings.
  • Per-process config — each session picks its own profile, no conflicts.
  • Escape hatch: anything not covered by first-class fields can go in env or settings.

Quick Start

npm i -g @unbyte/ccc

Create ~/.ccc/config.json:

[
  {
    "id": "some-id",         // name used to select this config
    "api": "https://api",    // provider base URL (required)
    "apiKey": "sk-ant-...",  // API key (optional if the provider allows it)
    "default": true,         // use this config when no id is given
    "models": {              // override model selection (optional)
      "default": "",
      "subagent": "",
      "haiku": "",
      "sonnet": "",
      "opus": ""
    },
    "thinking": {             // thinking config (optional)
      "effort": "high"        // low | medium | high | xhigh | max
    },
    "args": ["--debug"],      // extra args prepended to claude (optional)
    "env": {},                // extra env vars passed to claude (optional)
    "settings": {}            // additional Claude Code settings (optional)
  }
]

models also accepts a single string as shorthand — it applies to all model slots.

Then run:

ccc              # uses the default config
ccc another-id   # uses the "another-id" config
ccc -p foo       # passes args to claude

License

MIT