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

@any-nav/cli

v0.2.0

Published

Any-Nav CLI integration adapter (L0): discovers config, materializes generated navigation fragments into agent files (AGENTS.md and other registered formats). Owns all disk writes and exit codes.

Readme

@any-nav/cli

Point any-nav at any Markdown folder. No more hand-maintained index files.

The Any-Nav CLI integration adapter: it discovers config, answers navigation queries, and materializes generated listings into marked file sections. This package owns all disk writes and exit codes — the SDK (@any-nav/core) it wraps is read-only.

Install

npm install -g @any-nav/cli

Usage

any-nav init               # scaffold an any-nav.toml in the current folder
any-nav list [path]        # render the navigation listing for a folder
any-nav list --depth N     # bound the walk depth
any-nav list --write       # materialize the listing into the marked section
any-nav list --json        # machine face: pure JSON (routing projection) on stdout
any-nav help [command]     # command help, plus non-command help topics
  • Empty results are legal answers (exit 0) — this is a data-presentation tool, not a filter.
  • Exit ladder: 0 success (including rendered help/version), 1 runtime failure, 2 usage error.
  • --json keeps stdout a pure JSON stream: maintainer-class diagnostics go to stderr, consumer-facing notes ride the listing itself.

Config

any-nav.toml — states only exceptions; every key defaults:

  • local — curation list: paths expanded into the default listing.
  • budget — the context-budget guard (warns, never silently collapses).
  • scan — scan boundary policy, additive over the engine's built-in floor.

list walks up from the target folder for the nearest any-nav.toml; without one it lists on pure defaults.

License

MIT