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

@bbthorson/pinakes

v1.0.2

Published

Fictional continuity linter and AT Protocol record compiler

Readme

🏛 Pinakes

Pinakes is an open-source command-line utility and framework for building, linting, and maintaining fictional universes. It brings the software engineering principles of CI/CD and syntactic linting to creative writing—ensuring semantic continuity (timeline, casting, locations, and item custody) while compiling raw prose markdown into AT Protocol-compliant databases.

Pinakes runs downstream of the writing. Prose is the source of truth: when a finished chapter contradicts the codex, the chapter is right and the codex gets updated. Pinakes checks that the codex and the chapters still agree, and projects the story into records a reader-facing surface can use.

Documentation: bbthorson.github.io/pinakes

Quick start

npm install -g @bbthorson/pinakes

pinakes init my-universe
cd my-universe
pinakes lint      # check continuity: timelines, casting, co-presence, item custody
pinakes compile   # write AT Protocol records and their Lexicons to records/
📁 stories/book1/chapters/ch11_the_empty_stall.md:
  :18   [unresolved-entities] 🔴 ERROR: Unresolved reference to character 'Paolo Ferrante' in field 'characters_referenced'

FAIL — pinakes found errors.

Documentation

Developing

cd cli && npm ci && npm test

npm test builds from src/ and runs cli/test/ with Node's built-in test runner. The tests create throwaway universes in a temp directory and check what lint, compile, and context report and exit with. Commit the rebuilt cli/dist along with your change; CI checks that it matches a fresh build.

Edit this README, not cli/README.md: the build regenerates that copy (the one npm shows) from this file, with links made absolute. Conventions for working in the code, for people and coding agents alike, are in CLAUDE.md.

The documentation site is built from docs/ with Astro Starlight:

cd docs && npm ci && npm run dev