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/core

v0.2.0

Published

Any-Nav SDK: read-only core that scans Markdown folders into navigation, decides exposure within a context budget, renders injection fragments, and answers list/search/read. Adapters own all writes, processes, and protocols.

Readme

@any-nav/core

The Any-Nav SDK: scan a Markdown folder, guard it against a context budget, render navigation fragments, and answer list / search / read.

@any-nav/core is the read-only SDK behind Any-Nav. It composes the zero-dependency scan engine (@any-nav/scan — its full face is re-exported here) with: strict any-nav.toml config parsing, curation of default expansion via the config's local list, the budget-guard engine, rendering of the canonical navigation fragment for registered formats, and the query faces — list(path) with its rows / markdown renderings and JSON serialization, the search kernel, read, and the candidate feed.

Install

npm install @any-nav/core

Usage

The one-call face — list a folder under its nearest governing config (pure defaults when there is none):

import { listFolder, routingViewJson } from '@any-nav/core';

const listing = await listFolder('docs'); // optional query: { configPath, depth, commandRunner }
const machine = routingViewJson(listing);  // the routing projection as a pure JSON string

The full facade:

import { createAnyNav } from '@any-nav/core';

const app = await createAnyNav({ configPath: 'any-nav.toml' }); // or { config, cwd }

const sources = app.sources();                  // the config root as the single implicit source
const exposure = app.decideExposure(sources[0]); // budget-guard reading — warns, never collapses
const fragment = app.render(exposure, 'agents-md');
const next = app.materialize(current, fragment); // pure splice — the caller writes the file

Config

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

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

Boundaries this SDK keeps

  • Read-only over the filesystem: no writes, no processes, no network, no transport or LLM-client imports. materialize() returns new text — every write belongs to the adapter.
  • The unified list model: list(path) is the product face; governance and expansion live here, adapters only transport.
  • NavItem { name, description, locator } (from @any-nav/scan) is the only knowledge model.
  • Embedders that only need the scan engine can depend on @any-nav/scan directly and carry no SDK dependencies (smol-toml, fast-bm25 live on this package's config and search paths, not the engine's).

License

MIT