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

@distilled.cloud/github

v1.0.0-rc.6

Published

Readme

@distilled.cloud/github

Effect-native GitHub REST SDK, generated from GitHub's official OpenAPI description.

Spec source

The generator reads a single file:

specs/rest-api-description/descriptions/api.github.com/api.github.com.json

That file is ~13 MB. The repository it lives in, github/rest-api-description, is ~6.7 GB checked out — it ships every GitHub Enterprise Server version back to 2.18, each in both dereferenced and non-dereferenced form, in both JSON and YAML. Almost none of that is working tree we want: the git objects are only tens of MB, so the cost is entirely in materialised files.

The submodule is therefore sparse-checked-out to the one file we consume.

Fetching it

pnpm specs:fetch

Run this from packages/github. It initialises the submodule, narrows it to the single description file, and leaves ~13 MB on disk.

The footgun

Sparse-checkout config lives in local git config, not in the repository, so it does not travel with a clone. Two consequences:

  • A fresh pnpm specs:sync at the repo root — which does a plain git submodule update --init --recursive across every package — expands this submodule to the full 6.7 GB. It is not wrong, just very expensive.
  • specs:fetch itself checks out before it narrows, so it also passes through the full tree once on a cold clone.

To populate it from cold without ever materialising 6.7 GB, configure sparse checkout before anything is checked out:

SHA=$(git ls-tree HEAD packages/github/specs/rest-api-description | awk '{print $3}')
P=packages/github/specs/rest-api-description
rm -rf "$P" && mkdir -p "$P"
git -C "$P" init -q
git -C "$P" remote add origin https://github.com/github/rest-api-description.git
git -C "$P" sparse-checkout set --no-cone descriptions/api.github.com/api.github.com.json
git -C "$P" fetch --depth=1 origin "$SHA"
git -C "$P" checkout -q FETCH_HEAD
git submodule absorbgitdirs "$P"

The real fix is to mirror the one file we consume into alchemy-run/distilled-spec-github, the pattern neon / gcp / supabase already use, which removes the sharp edge entirely. Tracked in todo.md.