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

readme-kit

v1.1.5

Published

Component-based READMEs—like shadcn, but for your README. Install components from the CLI, write a template, run build. Output works on GitHub (SVGs as images).

Readme

readme-kit

Component-based READMEs—like shadcn, but for your README. Install components from the CLI, write a template, run build. Output works on GitHub (SVGs as images).

Install

npm install readme-kit --SD

In your repo (e.g. your GitHub profile repo):

# Creates .readme-kit folder in your project
npx readme-kit init

# Adds component
npx readme-kit add <component-name>

The idea is that you can create your own components in .readme-kit/components and they will work with your setup, you just have to refer to them as file's name. Also you can modify preinstalled components

# To build README.md use:
npm run build

How it works

Important: you have to create README.template.md and basically the package designed to modify only this file and do not touch README.md itself.

  • Placeholders like <!-- component name key=value --> are replaced at build time.
  • Components are Handlebars templates; SVG output is written to readme-assets/ and inlined as so GitHub renders them.
  • Icons come from the simple-icons package (installed with the project).