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

@paleo/docmap

v0.9.0

Published

A lightweight documentation system for AI agents and humans.

Downloads

2,770

Readme

@paleo/docmap

A lightweight documentation system for AI agents and humans. Keep project docs in a docs/ folder with YAML frontmatter, browse and read them from the terminal.

The CLI lists, reads, and validates docs, and ships its own authoring guide: run docmap --guide to learn the conventions for writing and organizing documents.

Inspired by the OpenClaw docs system, which uses Mintlify. This project doesn't depend on Mintlify.

Installation

Install the CLI as a dev dependency and add a docmap script:

npm install -D @paleo/docmap

In your package.json:

{
  "scripts": {
    "docmap": "docmap"
  }
}

In your AGENTS.md or CLAUDE.md file:

## Docmap - Seek Documentation

*Before* any investigation or code exploration, run `npm run docmap`, then read the relevant documentation. Mandatory for every task.

Bootstrapping a docs/ directory

To bootstrap a docs/ directory, wire docmap into a project, and migrate existing docs or skills, install the alignfirst-setup-guide skill temporarily and let an agent drive the setup:

npx skills add https://github.com/paleo/alignfirst --skill alignfirst-setup-guide

Then ask your agent:

Use your *alignfirst-setup-guide* skill. What are my options for bootstrapping a `docs/` directory in this project?

How It Works

  1. Uses a docs/ directory at your project root.
  2. All files and directories are preferably named in kebab-case.
  3. Lists most of the readable text files.
  4. .md files can start with YAML frontmatter. Add it when it adds value:
---
title: Short Title Here
summary: A short description of what this document covers.
read_when:
  - first situation when this document is useful
  - second situation
---

# Your Complete Title Here

...

| Field | Required | Description | | --- | --- | --- | | title | No | Display name shown in listings. Falls back to the first # heading in the document body when absent. | | summary | No | Short description. Omit if the title is self-explanatory. | | read_when | No | When to consult this document. Omit if the scope is obvious. |

Global Installation (non-JavaScript stacks)

Install the CLI globally to use it on non-JavaScript projects:

npm install -g @paleo/docmap

docmap -v

In your AGENTS.md or CLAUDE.md file:

## Docmap - Seek Documentation

*Before* any investigation or code exploration, run `docmap`, then read the relevant documentation. Mandatory for every task.

CLI

Run the CLI from the project directory that contains your docs/ directory.

# Short help, then the listing (lists recursively when the doc set is small)
docmap

# Full help
docmap --help

# Authoring guide (conventions for writing documents)
docmap --guide

# List one or more subdirectories
docmap dir-a
docmap dir-a dir-b

# List everything recursively
docmap --recursive

# Read one or more documents (frontmatter stripped)
docmap docs/dir-a/doc-1.md
docmap docs/dir-a/doc-1.md docs/dir-b/doc-2.md

# Mix directories and files in one call
docmap dir-a docs/dir-b/doc-2.md

# Search documents (any term matches; best matches first)
docmap --search "api endpoint"

# Validate all files (names, frontmatter)
docmap --check

# Use a custom docs root instead of docs/
docmap --root path/to/docs

20-document threshold

A bare invocation lists recursively when the tree holds fewer than 20 documents, and switchs to a top-level listing above that threshold. An explicit --recursive always walks the whole tree.

Classification

Each positional path is resolved against the docs root:

  • Existing directory → listed (honoring --recursive).
  • Existing file → read (Markdown files have their frontmatter stripped; other files are served verbatim).
  • Neither → a fuzzy basename search over listable files (so database.md resolves from anywhere in the tree). No match → a single ⚠ Not found: <path> line.

Listings display each path prefixed with the docs root relative to your working directory: docs/… by default, or whatever --root points to (e.g. --root config/docs shows config/docs/…). That prefix is optional on input and trailing slashes are tolerated: docs/dir-a/, docs/dir-a, and dir-a resolve identically