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

@nickgarlis/hoard

v0.1.0

Published

Fetch and store web content as markdown for use with local search and AI tools

Readme

hoard

Fetch web content and store it as markdown. Built to feed local search and RAG pipelines.

Each URL is fetched, stripped of noise, and written to a .hoard/ directory as a markdown file with YAML frontmatter. Re-running only refetches content that has changed.

Install

npm install -g @nickgarlis/hoard

Usage

Add a URL

hoard add https://pkg.go.dev/github.com/spf13/viper
hoard add https://pkg.go.dev/github.com/spf13/viper --tags config,golang

Creates hoard.json if it doesn't exist, fetches the URL immediately.

Fetch all sources

hoard fetch

Skips unchanged content (via ETags and content hashing). URLs removed from hoard.json have their files deleted.

List sources

hoard list

Remove a URL

hoard remove https://pkg.go.dev/github.com/spf13/viper

Options

All commands accept:

| Flag | Default | Description | |------|---------|-------------| | -c, --config <path> | hoard.json | Config file | | -o, --output-dir <path> | .hoard | Content store directory |

hoard fetch also accepts -f, --force to refetch everything regardless of cache.

hoard.json

{
  "sources": [
    {
      "url": "https://pkg.go.dev/github.com/spf13/viper",
      "tags": ["config", "golang"]
    }
  ]
}

Using with qmd

qmd is a local hybrid search engine for markdown files. hoard and qmd compose naturally — hoard writes .hoard/, qmd indexes it.

1. Fetch your sources:

hoard fetch

2. Register the store as a qmd collection (once):

qmd collection add .hoard --name hoard

3. Index and embed:

qmd update && qmd embed

4. Search:

qmd query "how do I configure viper"

After the initial setup, refresh with hoard fetch && qmd update && qmd embed whenever your sources change.