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

truedone

v0.1.1

Published

What a pull request's diff and its own tests show: one file, no dependencies.

Readme

truedone

npx truedone reads the current branch against the merge-base with the default branch and prints what the diff shows about its tests. npx truedone <PR link> does the same for a pull request through the GitHub API, with GITHUB_TOKEN if it is set; nothing is cloned. --json prints the truedone.verdict/1 result, and --fail-on <verdicts> exits 1 when the verdict is one of them. npx truedone init adds four lines for coding agents to AGENTS.md or CLAUDE.md, and npx truedone init --global adds them to your own ~/.claude/CLAUDE.md (and ~/.codex/AGENTS.md when ~/.codex exists), so they apply in every repository you work in.

--pr-line prints one line for a pull request description: the verdict, its reason and the link to the verdict's public page, which recomputes it for anyone who opens it. The fourth init line asks the agent to include it.

npx truedone report <PR link> prints a link to the wrong-verdict form on Truedone/truedone, filled with the pull request, its commits, the verdict and the version. Nothing is sent until you submit the form.

As a tool for agents (MCP)

npx truedone mcp serves the same check over the Model Context Protocol on stdio, as two tools: truedone_check_pr (a pull request link) and truedone_check_branch (the current branch). Each answers with the verdict line for a pull request description and the truedone.verdict/1 result. server.json at the repository root names its entry in the MCP registry, io.github.Truedone/truedone.

Claude Code:

claude mcp add truedone -- npx -y truedone mcp

Cursor (.cursor/mcp.json) and VS Code (.vscode/mcp.json, where the key is servers):

{ "mcpServers": { "truedone": { "command": "npx", "args": ["-y", "truedone", "mcp"] } } }

Codex (~/.codex/config.toml):

[mcp_servers.truedone]
command = "npx"
args = ["-y", "truedone", "mcp"]

Exit codes: 0 when a verdict is produced or --help (or -h) prints the usage, 1 when --fail-on matches, 2 for a usage error, 3 for an internal error.

This is the 0.1.1 preview: npx truedone --version prints truedone 0.1.1 (preview), and --help ends by naming it a preview.

The package is one file with no dependencies. Licence: Apache-2.0.