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

kumidocs

v0.20260711.145

Published

A developer-focused wiki/docs platform with zero database: all content stored in Git.

Downloads

11,870

Readme

KumiDocs

A wiki and docs platform for small dev teams. No database: all content is stored in Git.

Try it now

cd /any/git/repo
bunx kumidocs

That's it. Open http://localhost:5864.

KumiDocs serves the current directory as its content store. Every save becomes a git commit. No setup, no config files required.

No Bun? Install it with curl -fsSL https://bun.sh/install | bash

Features

  • Markdown editor: live split-pane, frontmatter, full history
  • Slide decks: set slides: true in frontmatter; scroll, paginate, spotlight, fullscreen
  • Code files: syntax highlighting via CodeMirror with language auto-detection
  • Full-text search: fuzzy, Ctrl+K palette
  • Real-time presence: edit lock, viewer avatars, live reload via WebSocket
  • Image library: drag-and-drop upload, usage tracking, safe delete
  • PDF export: pages (A4) and slide decks (landscape)
  • SSO: any reverse proxy that forwards an email header (oauth2-proxy, Authelia, etc.)

Options

Point KumiDocs at a different repo or change the port:

bunx kumidocs --repo /path/to/repo --port 8080

All options are also available as environment variables:

| Flag | Env variable | Default | Description | | ------------------- | -------------------------- | --------------------- | ---------------------------------- | | --repo | KUMIDOCS_REPO_PATH | cwd | Path to the git repository | | --port | KUMIDOCS_PORT | 5864 | HTTP/WS listen port | | --auth-header | KUMIDOCS_AUTH_HEADER | X-Auth-Request-User | Header carrying the user identity | | --auto-save-delay | KUMIDOCS_AUTO_SAVE_DELAY | 5000 | Auto-save debounce in ms | | --pull-interval | KUMIDOCS_PULL_INTERVAL | 60000 | Background git pull interval in ms |

Production (Docker Compose)

Copy compose.yaml to your server and set your OAuth credentials:

SSO_PROXY_CLIENT_ID=your_client_id
SSO_PROXY_CLIENT_SECRET=your_client_secret
SSO_PROXY_PROVIDER=github            # github | google | oidc | ...
SSO_PROXY_REDIRECT_URL=https://docs.example.com/oauth2/callback
SSO_PROXY_COOKIE_DOMAIN=example.com
SSO_PROXY_COOKIE_SECURE=true

Mount your content repo at /repo:

volumes:
  - /path/to/your/content-repo:/repo

Then:

docker compose up -d

The stack runs KumiDocs on port 5864 (internal) behind oauth2-proxy on port 5865 (public).

Repository layout

KumiDocs reads and writes directly to the git repo it's pointed at:

README.md              # home page
.kumidocs.json         # instance config (optional)
images/                # uploaded images
**/*.md                # doc pages and slide decks
**/*.{ts,js,...}       # code files (read-only viewer)

.kumidocs.json (optional)

{
  "instanceName": "MyDocs",
  "editors": ["[email protected]", "[email protected]"],
  "slideThemes": {
    "my-corp": {
      "bg": "#1a2744",
      "fg": "#e8edf8"
    }
  }
}

If editors is set, only those users can write. Everyone else is read-only. Omit the field to let all authenticated users edit.

Page frontmatter

---
emoji: 📄
description: Shown in search results
slides: true # treat as slide deck
theme: corporate # built-in or custom theme name
paginate: true # show slide N/total badge
---

Building from source

bun install
bun run build   # outputs to dist/
bun start       # runs the production build