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

cogdebt

v1.0.1

Published

Cognitive Debt Tracker — quantify and close the gap between vibe-coding and understanding

Readme

cogdebt

Cognitive Debt Tracker — quantify and close the gap between vibe-coding and understanding.

Built for developers who use LLMs to write most of their code and want to make sure they still understand what's in their codebase.

How It Works

cogdebt init     # Scan your codebase, discover topics
cogdebt quiz     # Answer questions about your actual code
cogdebt status   # See your coverage dashboard
  1. Scan — discovers topics in your codebase and identifies quiz-worthy files
  2. Quiz — asks you implementation questions about specific code blocks (~200 LOC each)
  3. Score — tracks which blocks you've demonstrated understanding of
  4. Decay — when code changes, only the affected blocks lose coverage (automatic, instant, no LLM)

Your score = covered blocks / total blocks per topic. Start at 0%, build up by taking quizzes, watch it decay as code changes.

Install

npm install -g cogdebt

Requires: Claude Code CLI installed and authenticated.

Quick Start

cd your-project
cogdebt init        # Scans codebase, discovers topics (~30s)
cogdebt quiz        # Pick topics, answer questions
cogdebt status      # See your dashboard

Commands

| Command | Description | |---------|-------------| | cogdebt init | Initialize cogdebt for the current project | | cogdebt quiz | Interactive quiz on your code | | cogdebt status | Coverage dashboard | | cogdebt decay | Check for code changes and update coverage | | cogdebt scan | Re-scan codebase for topic changes | | cogdebt history | View score change history | | cogdebt hooks | Set up git hooks and Claude Code status line |

Key Concepts

Block-Level Coverage

Files are split into ~200 LOC blocks. Each quiz question targets a specific block. Answering correctly covers that block, not the whole file. A 1000 LOC file needs ~5 correct answers to fully cover.

Smart Decay

When you change code, only the blocks containing the changed lines lose coverage. A 1-line fix in a 3000 LOC file only decays the ~200 LOC block around that line — not the whole file.

Decay runs automatically before quiz and status, so your scores are always current. It also runs as a git post-commit hook if you set up cogdebt hooks.

No LLM for Decay

Decay is instant and free. It parses git diff hunks to find changed lines and maps them to block indices. No API calls needed.

Scoring

  • Questions are scored as Got it / Partial / Missed
  • A block is "covered" when you score >= 50% on a question about it
  • Coverage = covered blocks / total blocks per topic
  • The goal is familiarity, not perfection

Data Storage

All data is stored locally in a .cogt/ directory (auto-added to .gitignore). Nothing is sent anywhere except the Claude API for question generation and answer evaluation.

Requirements

License

MIT