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

@edda-business/cli

v0.14.0

Published

Edda CLI — set up Edda, connect it to your coding agent, and read the Context API from your terminal

Readme

@opennous/cli

Nous CLI — set Nous up, connect it to your coding agent, and read the Context API from your terminal.

Get started

One command. It signs you in (creating your account if you don't have one), registers the Nous MCP server with the agent on your machine, and hands off. The same command on macOS, Linux, and Windows (needs Node 18+):

npx @opennous/cli@latest init

Then tell your agent "set up my Nous workspace" — it reads your project, finds your ICP (or drafts one), and syncs it. On self-host, add --url https://api.yourdomain.com.

Event tracking

nous track init detects your stack (Next.js, Node, Python), writes a small nous.js (or nous.py) module with three helpers, and updates your .env:

  • trackSignup({email, ...}) — fires interaction.signed_up + initial state.stage
  • handleStripeEvent(event, {customerEmail}) — fires interaction.subscription_started / updated / canceled and flips state.stage (Customer / Churned)
  • track(focus, property, value) — escape hatch for any other event

The generated module is plain code you own. Read it, edit it, or delete it. (This was nous install; that name still works but is deprecated.)

Other commands

nous auth login --key <your-key>     # save your API key
nous context <email>                  # engineered context for a person
nous account <email>                  # full record with epistemics + timeline
nous record <email> --property X --value Y
nous query --property stage --value Customer
nous attention                        # surface what changed recently
nous verify <email> <property>        # confirm a claim is current

Run nous --help for the full list.

Auth

NOUS_API_KEY env var, or nous auth login --key <key>. Mint a key at app.opennous.cloud → Settings → API Keys.

Self-hosting

Set NOUS_API_URL to your own deployment.

License

AGPL-3.0