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

@spader/dotllm

v1.3.2

Published

A simple CLI to clone, manage, and link repositories for LLM reference

Readme

dotllm

dotllm manages a system-wide cache of commonly referenced repositories and provides a beautiful command line for linking them anywhere on your system

> tree .llm/reference/
.llm/reference/
├── cloudflare-docs -> /home/spader/.local/share/dotllm/store/cloudflare-docs
├── cuda-toolkit -> /home/spader/.local/share/dotllm/store/cuda-toolkit
├── ghostty -> /home/spader/.local/share/dotllm/store/ghostty
├── node-llama-cpp -> /home/spader/.local/share/dotllm/store/node-llama-cpp
├── opencode -> /home/spader/.local/share/dotllm/store/opencode
└── sprites-docs -> /home/spader/.local/share/dotllm/store/sprites-docs

LLMs work best with references. If you're like me, every project has loose repositories lying around half a dozen places because some LLM needed it.

Instead, keep a cache of such repositories and use dotllm to link them to .llm. Check in .llm/dotllm.json, and a simple dotllm sync will restore all of your references.

installation

bun install -g @spader/dotllm

usage

Register a repository (by HTTPS, SSH, or local path)

dotllm add https://github.com/tspader/dotllm.git

In any directory, use the interactive CLI to edit which repositories are linked to .llm/reference

dotllm link

Check in .llm/dotllm.json. Then, on a fresh clone, link the repositories to your local copy

dotllm sync