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

todos-finder

v1.0.0

Published

Scan any codebase for TODO/FIXME/HACK/XXX/NOTE comments and display them beautifully

Readme

todos

Scan any codebase for TODO/FIXME/HACK/XXX/NOTE comments and display them beautifully.

Find every forgotten TODO in your codebase — who wrote it, how old it is, and whether anyone still cares. Git blame integration, priority detection, and an interactive triage mode to force decisions on stale comments.

Install

npm install -g todos-finder

Or run it directly:

npx todos-finder

Usage

Scan current project

todos

Shows all TODOs in a color-coded table with comment text, file path, line number, author (via git blame), age, and priority.

Filter to your TODOs

todos mine

Matches your git config user.name.

Find stale TODOs

todos stale        # older than 6 months
todos stale 30d    # older than 30 days
todos stale 1y     # older than 1 year

Hot TODOs

todos hot

TODOs in files that changed in the last 14 days — the ones that actually matter.

Stats dashboard

todos stats

Breakdown by type, author, age, priority, and trend over time.

Triage mode

todos clean              # triage all TODOs
todos clean --mine       # only yours
todos clean --stale 3m   # only stale ones
todos clean -t HACK      # only HACKs

Walk through TODOs one by one and decide their fate:

  • Skip — leave as is
  • Open — open in your editor at the exact line, then mark as done or skip
  • Resolve — remove the comment (the work is done)
  • Won't fix — convert to NOTE: with a reason

Auto-detects your editor (Cursor, VS Code, Vim, Sublime, JetBrains, etc.) from running processes.

Export

todos export --md                # markdown to stdout
todos export --md -o todos.md    # markdown to file
todos export --gh                # create GitHub issues (interactive picker)

Watch mode

todos watch

Shows new TODOs as they appear in changed files.

Options

-d, --dir <path>     directory to scan (default: cwd)
-s, --sort <field>   sort by: priority, age, file, author
-t, --type <types>   filter by type (comma-separated)
--no-context         hide surrounding code lines
--no-blame           skip git blame (faster)

What it detects

| Keyword | Color | Default Priority | |----------|--------|-----------------| | TODO | yellow | P3 | | FIXME | red | P2 | | HACK | orange | P2 | | XXX | red bold | P1 | | NOTE | blue | P4 | | BUG | red bold | P1 | | OPTIMIZE | cyan | P4 |

Priority is elevated by TODO(P0), TODO(urgent), FIXME!!, etc.

Supported languages

JavaScript, TypeScript, Python, Go, Rust, Java, Ruby, C/C++, C#, Swift, Kotlin, Scala, Dart, PHP, Lua, SQL, Haskell, Elm, Elixir, Shell, YAML, TOML, HTML, CSS/SCSS, Vue, Svelte, Astro, and more.

Comment patterns (//, #, --, /* */, <!-- -->, etc.) are matched per file extension.

How it works

  1. Scanner walks the directory tree, respects .gitignore, and extracts comments using language-aware regex patterns
  2. Git integration runs git blame on each TODO line to get author and timestamp
  3. Display renders with color-coded tables, priority labels, and contextual code snippets

No AST parsing, no build step, no config files. Just regex and git.

License

MIT