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

static-anthology

v2.0.1

Published

Static site renderer for project showcases

Readme

Static Anthology

This project allows the user to easily host multiple web projects as subpages on a single website. Pages can be specified using a sitemap json file, with support for projects on local filesystems as well as on GitHub.

Detecting Projects: Static Web App Manifests

In order to determine if a project is a static web app, each source should have a file, swa_manifest.json in the root directory. This json file must contain the following fields:

{
    "title":"The title of the web app",
    "root":"The root directory of the repository containing static content",
    "directory": "The output directory of the static subpage"
}

Additionally, tile images for each site are loaded from swa_tile.png if present.

Static Resources

Static resources for the root page may be added to static_src. These will be copied as-is into the root of the output directory. This is a good location for styles, images, and any other root-level web assets.

Templates

The rendering process uses three template files:

  • index.njk - determines the base landing page. Contains multiple tiles.
  • folder.njk - folders store multiple tiles.
  • tile.njk - a single tile. One tile is produced per web app.

Configuration

Configuration for any command-line arguments can also be supplied by adding a config.json file in the current directory. This is the recommended place for your GitHub username and token.

Running the Compiler

Once configured, run

npx static-anthology
OR
npx static-anthology compile

Generating a SiteMap from GitHub

If you would like to generate a sitemap from all of the static web apps on a user's GitHub account, you can run

npx static-anthology source

Make sure to configure a username and token.