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

@e0ipso/ai-knowledge-base

v0.27.0

Published

Builds and maintains a per-repo knowledge base from AI coding sessions, for use with Claude Code.

Readme

@e0ipso/ai-knowledge-base

npm license: MIT

A team-shared, git-native knowledge base for AI coding sessions on Claude Code, Codex CLI, Cursor, and OpenCode. Knowledge lives in your repo as plain markdown, not in a per-user database on one developer's laptop, so it propagates to teammates through git pull and is reviewable like code in PR diffs and commit history.

No daemons. No services. No external runtimes. Just Node + git.

Your AI conversations produce a steady stream of project-specific knowledge (conventions, gotchas, named modules, decision rationale), and most of it evaporates when the session ends. This tool captures it, asks a human to curate it, commits it to the repo, and injects it back into every future session.

Quick start

npx @e0ipso/ai-knowledge-base init --harnesses claude
npx @e0ipso/ai-knowledge-base doctor

Then code normally. When you want to turn captured material into knowledge nodes, run /kb-curate inside your harness session (also /kb-add, /kb-bootstrap). Prefer the in-session skills. They're context-aware and the only path that walks you through conflict resolution. The matching CLI commands (npx @e0ipso/ai-knowledge-base curate, etc.) exist for scripts and CI but skip the interactive parts. New nodes appear in nodes/; review with git diff and commit the ones you want to keep.

Seed from existing docs

If your repo already has READMEs, ADRs, or module docs, seed the KB from them. Inside a harness session:

/kb-bootstrap

The scan walks the repo root, filtered by .kbignore (generated by init, uses gitignore-style syntax). Edit .kbignore to exclude directories you don't want scanned. Review the resulting nodes under nodes/ with git diff and commit the ones you want to keep.

Documentation

Full documentation: https://mateuaguilo.com/ai-knowledge-base

For maintainers of this package itself, see CONTRIBUTING.md.

License

MIT