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

lorecode

v0.1.7

Published

Lore — a live feature map of what your AI coding agent builds

Readme

Lore

A live map of what your AI agent builds.

Lore watches your codebase as Claude Code (or Cursor, Windsurf, etc.) edits it, and keeps a live feature map in sync — so you always know what your app does, what's broken, and what changed.

lorecode.vercel.app


What you get

  • Live feature map — every feature your app has, updated automatically as your AI codes
  • Error diagnosis — runtime errors get mapped to the broken feature with a plain-English cause and a ready-to-paste fix prompt
  • Security auditlore audit scans for common vulnerabilities and shows how to fix them
  • MCP integration — your AI agent reads the map directly so it understands your app before touching it

Install

npm install -g lorecode

Setup

  1. Go to lorecode.vercel.app, create a project, and copy your Project ID and Ingest Token.

  2. In your project directory:

lore init <project-id> --token <ingest-token>

That's it. Lore will:

  • Write .claude/lore.json (added to .gitignore automatically)
  • Install a Claude Code hook so the map updates on every file edit
  • Register an MCP server in .mcp.json so your AI can read the map
  • Add the error collector to your index.html
  • Build your first map

For Cursor, Windsurf, or other tools

lore init <project-id> --token <ingest-token> --tool other

Then run this while you code:

lore watch

Commands

| Command | What it does | |---------|-------------| | lore init <id> --token <t> | Set up this repo (config, hook, first map) | | lore sync | Analyze changes and push an updated map | | lore watch | Watch for file changes and sync automatically | | lore audit | Scan your codebase for security issues | | lore mcp | Start the MCP server (auto-started by Claude Code) |


How it works

Every time your AI edits a file, the Claude Code hook calls lore sync. Lore parses your codebase, extracts the feature map (what features exist, which files implement them, how they connect), and pushes it to the Lore web app in real time.

The web app shows you a live node graph. When a runtime error hits your app, the error collector sends it to Lore, which diagnoses it automatically and marks the broken feature red on the map.


License

MIT