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

wiki-plugin-shortlink

v0.1.0

Published

Federated Wiki - Shortlink Plugin — mint memorable three-word short URLs for wiki lineups, with expiry, single-use, and revocation

Readme

wiki-plugin-shortlink

Memorable short URLs for Federated Wiki lineups — three words drawn from Hitchhiker's Guide lore, in the style of what3words:

http://localhost/plugin/shortlink/towel-frood-zarquon
→ 302 → http://localhost/view/welcome-visitors/plan.localhost/roadmap

Links carry a per-link TTL (1d, 1w, 1m, never), may be single-use (burned before the redirect is sent), and are revocable from the visible register — a wiki page carrying the shortlink item, which renders live from the store and offers copy/revoke/mint buttons.

Shape

  • Farm-mounted API (declared via fedwiki.api, mounted by wiki-plugin-farm): /system/api/shortlink/ list.json, expand.json, words.json, and the owner-gated mint.json / revoke.json.
  • Plugin server (server/server.js, CommonJS): the one route the farm mount can't host because it must not end in an extension — GET /plugin/shortlink/{key}.
  • Client item: the register table.

Store

One machine-global JSON file, ~/.wiki-shortlinks/links.json (SHORTLINK_STORE overrides; deliberately not per-site — a lineup spans sites, and with WIKI_EXTRA_FARMS a farm-root-derived path would split the store). External writers are first-class: edit the file (atomic rename, please) and the server picks it up by mtime with no restart — this is how the shortlink-mint skill mints AI-chosen keys.

Words and entropy

server/lore.txt (~230 HHGG words) feeds memorable keys; server/wordlist.txt (~1700 merged words) feeds uniqueness checks and the uniform random suffix. Three lore words are memorability, not security (~24 bits). A link minted with capability=true gets two uniform random words appended (~45 bits total), and every lookup sits behind a per-IP token bucket plus a global failed-lookup circuit breaker. Failure responses are identical for unknown/expired/revoked/used keys.

Test

npm test

runs the state logic against a temp store: mint, collision, TTLs, expiry, single-use burn, revoke, mtime re-read, purge.