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

@danieltechdev/blueprint-tracker

v0.1.1

Published

Pure parser, board model, and validator for the cosmere estate blueprint corpus (Blueprint 35/41) — the single source of truth shared by the bp CLI, the estate-kb MCP, and the docs BlueprintBoard.

Downloads

187

Readme

bp-tracker

Blueprint tracker for the estate blueprint corpus — Blueprint 35, Milestone M1.

The blueprint markdown frontmatter is the single source of truth. Everything here is a projection of it: the bp CLI dashboard (M1), the docs-site board (M2), and the one-way task-MCP projection (M3). The board is a mirror, never a master — bidirectional sync is forbidden by construction (BP35 minefield 1).

Layout

  • src/core/ — pure functions, zero dependencies, no fs/network: parseBlueprint, validateCorpus, buildBoard, taskIdFor + planTaskSync + applyTaskSyncPlan, serializeFrontmatter.
  • src/cli/ — the bp CLI. All file access goes through the injectable BlueprintStore interface; the task projection goes through the injectable TaskSink interface (M1 ships in-memory/no-op implementations only; real Firestore wiring is M3).
  • src/index.ts — public API consumed by the M2 Astro endpoint.

CLI

bp list                     list all blueprints with frontmatter
bp board                    render the blueprint board in the terminal
bp lint                     validate the corpus (exit 1 on errors)
bp status <id> <state>      set a blueprint's status (surgical frontmatter edit)
bp link <id> <url>          append a link to a blueprint's frontmatter
bp backfill [--write]       infer frontmatter for legacy files (dry run by default)

Default corpus directory: /root/knowledge-base/fable-blueprints (override with --directory). The KB file is always the master; the docs-site copy under danieltech-kb/src/content/docs/blueprints/ is downstream and gets overwritten by the sync script (BP35 minefield 5) — never edit it.

bp status / bp link are the only writers and perform a surgical frontmatter edit: only the frontmatter block is replaced, the body bytes stay verbatim (guarded by a fast-check round-trip property). bp backfill is a dry run that prints a review table; nothing is written without --write and a human reading that table first.

Gates

npm run lint && npm test && npm run typecheck

Plus npm run analyze:deps (dependency-cruiser enforces that src/core never imports fs/network/CLI code), npm run analyze:deadcode (knip), npm run lint:secrets (secretlint).