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

@stats-forge/github-stats-forge-core

v0.15.0

Published

Dynamically generate stats for your GitHub readme

Readme

@stats-forge/github-stats-forge-core

The library behind GitHub Stats Forge: it turns GitHub and WakaTime data into SVG cards.

Nothing here reads the environment or the filesystem — you pass a config in, you get a string of SVG back — so it behaves the same under Node, in a browser and under a test runner. It is what the CLI, the action and every self-hosted instance call.

npm install @stats-forge/github-stats-forge-core
import { CardConfig, stats } from '@stats-forge/github-stats-forge-core/api';

const config = new CardConfig({ pats: [{ name: 'PAT_1', value: process.env.PAT_1! }] });

const result = await stats({ username: 'anuraghazra', theme: 'cobalt_dark' }, config);

// `content` is an SVG either way: a failure is a card that says what went wrong.
response.setHeader('Content-Type', 'image/svg+xml');
response.end(result.content);

Requires Node ^24 || >=26.

[!TIP] The library documents the handlers, CardConfig, the error codes and the entry points. Every card has a page of its own.

Acknowledgements

It continues the work of github-stats-extended, which is itself based on github-readme-stats.