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

@veryhappythings/prize

v0.3.0

Published

Augment and structure human PR reviews with LLM analysis

Readme

Prize

Prize is an AI augmented pull request review tool.

As usage of AI agents grows, I'm receiving more pull requests, and those pull requests are getting larger. Prize reads the PR and uses LLMs to contextualise the changes, presenting them in a way that makes it easier to understand the changes and their implications.

The narrative of a pull request is important. Some people I've worked with are masters at telling stories with their diffs, explaining the change commit by commit in a way that helps the reviwer understand the change. AI agents generally do not do this. We can help them.

Prize screenshot

Examples

Usage

npx @veryhappythings/prize <pr-url>

Or install globally:

npm install -g @veryhappythings/prize
prize <pr-url>

Requires Bun to be installed.

Example:

ANTHROPIC_API_KEY=<key> GITHUB_TOKEN=<token> npx @veryhappythings/prize https://github.com/kubernetes/kops/pull/18204

prize — kubernetes/kops#18204

✓ Fetched PR: azure: Add Workload Identity support
✓ Overview analysis complete
✓ Found 8 logical pieces
  Analyzing 8 pieces...
    [1/8] Analyzed: vendor-dependency
    [2/8] Analyzed: api-types-and-conversion
    [3/8] Analyzed: azure-tasks
    [4/8] Analyzed: issuer-discovery
    [5/8] Analyzed: workload-identity-model-builder
    [6/8] Analyzed: azure-blob-vfs
    [7/8] Analyzed: integration-test
    [8/8] Analyzed: addon-templates
✓ Detail analysis complete
✓ Generated: /Users/mac/.prize/kubernetes-kops-18204/site/index.html

Serving at http://localhost:3000
Press Ctrl+C to stop.

From source:

bun install
bun run build
ANTHROPIC_API_KEY=<key> GITHUB_TOKEN=<token from github> ./dist/prize https://github.com/kubernetes/kubernetes/pull/138214

You can configure your LLM provider with environment variables:

LLM_PROVIDER = 'anthropic' | 'openai' | 'bedrock'
LLM_API_KEY or ANTHROPIC_API_KEY
LLM_BASE_URL
LLM_MODEL (defaults to claude-opus-5-5 for anthropic, anthropic.claude-opus-5-5 for bedrock)
AWS_REGION (if using Bedrock)

Bedrock example:

AWS_REGION=eu-west-2 AWS_PROFILE=<profile> LLM_PROVIDER=bedrock LLM_MODEL=eu.anthropic.claude-opus-4-7 ./dist/prize https://github.com/kubernetes/kubernetes/pull/138214

Limitations

  • Currently only supports GitHub
  • Supports OpenAI compatible APIs, Anthropic, and AWS Bedrock

How it works

Prize uses the GitHub API to fetch the pull request data, including the changed files and their contents. It then uses an LLM to build an overview of the changes, followed by a structure that breaks up the change into narratively coherent sections. Finally, the LLM is called for each section to contextualise it in place. The result is a primer on the change that flows, rather than an alphabetically ordered list of files that makes no sense.

The results of the API calls and LLM calls are cached in ~/.prize. If you run Prize on the same PR it will only recalculate the pages if the PR has changed.