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

@devon-church/sauerkraut

v1.0.9

Published

A GitHub NPM module reference test

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

devon-churchdevon-church

Keywords

Readme

Sauerkraut 🍲

npm version build status

An AWS CodeBuild sequence to simultaneously create package install hooks in NPM, GitHub and AWS S3.

Pipeline ⚙️

sauerkraut-infrastructure

Usage 🎛️

S3

Holds .tgz files associated to each released version of that package.

Usage

Install version 1.0.8 of the package.

npm install "https://s3.amazonaws.com/sauerkraut/1.0.8.tgz"

Versioning

Package versions are targeted via their associated file names e.g 1.0.8.tgz

Github

Holds the necessary raw assets required for NPM to verify the package.

  • package.json
  • package.js (The CLI Hook)
  • dist/* (The package content)

Usage

Install version 1.0.8 of the package.

npm install "git://github.com/devonChurch/sauerkraut.git#v1.0.8"

Versioning

Package versions are targeted via their associated tag names e.g #v1.0.8

NPM

Uses the traditional NPM installation process with this package residing under the @devon-church scope.

Usage

Install version 1.0.8 of the package.

npm install @devon-church/[email protected]

Versioning

Package versions can be targeted via NPM's version selector syntax e.g @1.0.8

Note 💡

Unlike NPM, the package assets stored on GitHub and AWS S3 are statically referenced. This means that you can not request a dynamic server range as there is no registry implementing version reconciliation.