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

@fusedmodel/ncc-cli

v0.1.2

Published

npm wrapper for the NCC CLI: locates (or downloads) the platform Rust binary and runs it.

Readme

@fusedmodel/ncc-cli

npm wrapper for the NCC command line. It locates the platform Rust binary — or downloads it once — and hands over stdin/stdout/signals unchanged.

npx @fusedmodel/ncc-cli --help

Or install it globally:

npm i -g @fusedmodel/ncc-cli
ncc search --kind skill

The installed command is ncc.

What it does

NCC is a registry for capability artifacts (API / Skill / MCP / Harness / Plugin / Scaffold). The CLI talks to the registry at ncc.ai or to your own deployment.

| Command | Purpose | | --- | --- | | ncc register · ncc login · ncc logout · ncc me | account and session | | ncc ns list · ncc ns create --slug … | namespaces | | ncc publish | publish an artifact (--kind skill --name X --file ./x.SKILL.md) | | ncc search [query] [--kind api] | browse the catalog | | ncc info <id \| @org/slug> | artifact details | | ncc download · ncc install | fetch bytes, or install into ~/.ncc/packages | | ncc key create\|list\|revoke | API keys | | ncc living | device heartbeat (Living); --daemon to report periodically | | ncc terminal · ncc upgrade | terminal console, in-place self-upgrade |

Where the binary comes from

This package ships a launcher, not the binary. bin/ncc.js resolves in this order and never silently switches source:

  1. NCC_BIN (explicit path)
  2. vendor/ncc-<os>-<arch> shipped inside the package
  3. ~/.ncc/bin/ncc (previously installed)
  4. cli/target/release/ncc — the single-repo development case

If none exist it downloads once from NCC_RELEASE_BASE (default: this repo's GitHub Releases) into ~/.ncc/bin/ncc. postinstall attempts the same download, but fails soft — a broken or offline install still leaves you with a working launcher that retries on first run.

Asset names follow ncc-<os>-<arch>[.exe], with os ∈ {darwin, linux, windows} and arch ∈ {x86_64, arm64}. That naming is a contract shared with .github/workflows/release.yml and scripts/build-release.sh — change one, change all three.

Just want the source

git clone https://github.com/fusedmodel/ncc.git && cd ncc/cli
cargo build --release
./target/release/ncc --help

License

Apache-2.0.