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

create-portable-llm-wiki

v0.1.0

Published

Scaffold a fresh Portable LLM Wiki content repo — markdown starter pages, .gitignore, README, and git init — ready to push to GitHub and one-click deploy on Render.

Readme

create-portable-llm-wiki

Scaffold a fresh Portable LLM Wiki content repo on your machine.

This is the "I want my own wiki" entry point. One command creates a local folder with starter markdown pages, a .gitignore, a mini README.md, and an initialized git repo — ready for you to push to GitHub and one-click deploy on Render.

Usage

npx create-portable-llm-wiki my-wiki
cd my-wiki
git remote add origin https://github.com/<you>/my-wiki.git
git push -u origin main

Then click Deploy to Render on the main project README and paste your repo URL into the WIKI_GIT_REMOTE env var.

What you get

my-wiki/
├── .gitignore
├── README.md           ← mini README pointing at the main project
├── wiki/
│   ├── index.md        ← the catalog
│   ├── purpose.md      ← why this wiki exists (rewrite in your voice)
│   ├── log.md          ← append-only op log
│   ├── entities/
│   │   └── about-me.md
│   ├── concepts/
│   │   └── first-principle.md
│   ├── decisions/      ← (empty, .gitkeep)
│   ├── projects/       ← (empty, .gitkeep)
│   ├── sources/        ← (empty, .gitkeep)
│   └── queries/        ← (empty, .gitkeep)
└── raw/
    └── README.md       ← how raw/ works

All starter pages are tier: public so the deployed wiki has something to show on first load. Edit, add your own pages, or run the wiki's import wizard (/connect → Import) to bootstrap 8–12 pages from a resume or LinkedIn paste.

Why a scaffolder?

Forking the main repo and editing pages in place works, but it muddies the boundary between the app (which gets updates) and your content (which is yours forever). Keeping content in a separate repo means:

  • You can keep your wiki content private even though the app is OSS.
  • You can swap the deployed app for a newer version without touching your pages.
  • WIKI_GIT_REMOTE on the backend points at your content repo. Cold starts re-clone it; mutations push back to it. The app forgets you; your content survives.

Local development

git clone https://github.com/professorpalmer/portable-llm-wiki
cd portable-llm-wiki
./scripts/init.sh         # choose "Point at a path you already have"
                          # → /absolute/path/to/my-wiki
./scripts/dev-backend.sh  # in one terminal
(cd frontend && npm run dev)  # in another

Not yet on npm

This package isn't published to npm yet — invoke it directly from a clone for now:

git clone https://github.com/professorpalmer/portable-llm-wiki
node portable-llm-wiki/create-portable-llm-wiki/bin/cli.js my-wiki

(Publication is gated by prepublishOnly in package.json; the package will be npx-able once it ships.)

License

MIT © professorpalmer