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

acentecom-cc

v0.1.2

Published

Install your Acentecom-curated Claude Code setup with one command.

Readme

acentecom-cc

Install Acentecom's curated Claude Code setup — skills, agents, MCP servers, tools, and packs — from the internal acentecom·cc hub.

Internal tool: the hub is invite-only. The CLI is public so npx works, but every command needs an approved Acentecom account.

Quick start

npx acentecom-cc login      # browser device flow — approve this machine
npx acentecom-cc find       # browse the catalog, pick & install
npx acentecom-cc install    # install your default setup into ~/.claude

Daily use

| command | what it does | | --- | --- | | find [query] | search the catalog; multiselect to add + install | | add <name> | add an item to your setup, then install it | | list / status | installed items, available updates, manual steps | | update [name…] | reinstall only items whose version moved | | remove <name…> | drop from your setup + delete local files | | uninstall | remove everything the lockfile tracks | | logout | revoke this machine's token on the hub |

Add -p / --project to target ./.claude in the current repo instead of ~/.claude (own lockfile, committed with the project).

Curation (admin/dev)

acentecom-cc init my-skill                  # scaffold a SKILL.md (or --agent)
acentecom-cc publish my-skill --publish     # import into the catalog
acentecom-cc publish --from owner/repo      # import from any git repo
acentecom-cc publish-mcp <slug> --command "claude mcp add …"

MCP/tool entries are info-cards: the hub stores only the official install command — Claude Code runs the install and owns any OAuth. Secrets never touch the hub; anything sensitive is prompted for locally.

Point the CLI at another hub with ACENTECOM_CC_HUB=<url>.