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

@python/blog-utils

v0.0.2

Published

Shared Astro components for the PSF, PyPI, and Python Insider blogs.

Readme

@python/blog-utils

Shared Astro components for the three PSF-family blogs: psf/blog, blog.pypi.org, and Python Insider.

Each site vendored its own copy of these components, so fixes landed in one repo and never reached the other two. This package holds the copies that are identical across all three, so a fix ships once.

Install

bun add @python/blog-utils

Astro compiles the .astro sources directly — the package has no build step.

Use

---
import Pagination from "@python/blog-utils/components/Pagination.astro";
import Pep from "@python/blog-utils/components/references/Pep.astro";
import { externalIcon } from "@python/blog-utils/components/references/icons";
---

<Pagination currentPage={2} totalPages={9} baseUrl="/blog" />

Two things the consuming site must provide

1. Import the badge styles. The reference components are styled by a stylesheet the package ships, scoped to .prose (a badge outside a .prose container is deliberately unstyled):

@import "@python/blog-utils/styles/references.css";

It covers every reference type the remark plugin detects.

CommandPalette needs its own stylesheet too — it is built from .cmdk-* classes rather than utilities, so without this it renders as unstyled text:

@import "@python/blog-utils/styles/command-palette.css";

2. Tailwind must scan this package. Tailwind v4 skips node_modules, so the classes in these components are invisible to it by default. Add to your global CSS:

@source "../../node_modules/@python/blog-utils/src";

3. Pagination reads two theme tokens so each site keeps its own palette:

@theme {
  --color-py-blue: #306998;    /* active page, light mode */
  --color-py-blue-dm: #ffd43b; /* active page, dark mode  */
}

Contents

| Export | Notes | | --- | --- | | components/PythonLogo.astro | byte-identical across all three sites | | components/Pagination.astro | token-based variant, from psf/blog | | components/references/{Docs,GhRepo,GhUser,Pep,PyPi}.astro | byte-identical across all three sites | | components/references/icons | superset of the three copies | | lib/og-fonts | Inter 400/600/700 loader for satori OG images |

Component gallery

Every component, in every state and placement, on one page:

make dev      # or: make preview

The gallery lives in demo/ and imports the package sources by relative path, so it exercises the same files npm ships. It is never published — files in package.json limits the tarball to src/.

Run make help for the full target list.

Releasing

Publishing runs from GitHub Actions with npm Trusted Publishing (OIDC) — there is no npm token to leak. See .github/workflows/publish.yml.