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

ossperks

v0.3.2

Published

CLI to check if your project qualifies for OSS perk programs based on their guidelines.

Readme

Check if your project qualifies for open-source programs — across GitHub, GitLab, Codeberg, and Gitea.

Install

# Run without installing
npx ossperks

# Install globally
npm install -g ossperks
# or
pnpm add -g ossperks

Commands

check

Check your project's eligibility across all supported OSS programs.

# Auto-detect repo from package.json or git config
ossperks check

# Specify a repo explicitly
ossperks check --repo vercel/next.js

# Check a GitLab, Codeberg, or Gitea repo
ossperks check --repo inkscape/inkscape --provider gitlab
ossperks check --repo forgejo/forgejo --provider codeberg
ossperks check --repo go-gitea/gitea --provider gitea

# Output results as JSON
ossperks check --repo vercel/next.js --json

What gets checked automatically:

  • License type (permissive, OSI-approved, copyleft)
  • Star count thresholds
  • Fork and private repo detection
  • Tech stack requirements (e.g. Convex, Neon, Algolia packages in package.json)
  • Hosting hints (e.g. presence of vercel.json)
  • Project age

What requires manual review:

  • Non-commercial use
  • Community size
  • Code of conduct
  • Subjective or role-based criteria

list

List all available OSS programs.

ossperks list

# Filter by category
ossperks list --category devtools

# Output as JSON
ossperks list --json

show

Show details for a specific program by its slug.

ossperks show vercel
ossperks show sentry
ossperks show github-copilot

search

Search programs by name, description, tags, or perks.

ossperks search "database"
ossperks search "ci cd"

categories

List all available program categories.

ossperks categories
ossperks categories --json

Environment Variables

Set these to avoid API rate limits when checking repos:

| Variable | Description | | -------------- | ---------------------------- | | GITHUB_TOKEN | GitHub personal access token | | GITLAB_TOKEN | GitLab personal access token |

GITHUB_TOKEN=ghp_... ossperks check --repo your-org/your-repo

Development

See the CONTRIBUTING.md for development setup and commands.