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

prelo

v0.2.0

Published

The open-source CMS for websites built by AI and run by humans. One SQLite file, one uploads folder, one Node process.

Readme

Prelo

The open-source CMS for websites built by AI and run by humans.

Modern stacks made websites fast to build and impossible to hand over — Prelo ends with a WordPress-style studio your client already knows. One Node process, one SQLite file, one uploads folder. MIT licensed, self-hosted, zero external services.

npx create-prelo my-site
cd my-site && npm run dev        # site + studio + API on http://localhost:3300

Website: prelo.dev · Source: github.com/anderdigital/prelo

What it is / isn't

  • Is: a CMS that serves the whole site from one process — point site: in the config at a render module or at a request handler that mounts Next/Astro/anything on the same port (or omit it and go fully headless). Familiar admin (/studio, /wp-admin redirects there), a JSON REST API, roles (admin/editor/author), scoped API keys for AI agents with a full audit log, local media with on-upload resizing, magic-link invites, and a content model defined in one file (cms.config.js).
  • Isn't: a page builder, a theme marketplace, or a plugin ecosystem. Features are AI-written code in your own repo (hooks:, routes:, and x_-prefixed tables). The frontend is yours — any framework that can fetch.

CLI

| Command | What it does | | --- | --- | | prelo dev | Start site + studio + API locally; restarts on config/site changes | | prelo start | Production mode (what the Dockerfile runs) | | prelo add <plugin> | Fetch a plugin spec from prelo.dev/plugins into plugins/<name>.md for your agent to implement | | prelo check | Validate cms.config.js and print the parsed schema | | prelo doctor | Check config, database, Node version, sharp and disk | | prelo create-admin | Create the first admin user | | prelo user add / reset | Manage studio users via one-time links | | prelo key create | Mint a scoped API key for an agent (shown once, stored hashed) | | prelo seed | Load content/seed.json into the database | | prelo export [dir] | Copy the whole site state (db + uploads) to a folder | | prelo docs [topic] | Print reference docs, written for AI agents and humans |

For AI agents

Everything is designed to be driven unaided: prelo docs <topic> prints version-matched reference docs, /llms.txt describes the live API, and every error carries a hint naming the fix.

Plugins

A Prelo plugin is a markdown spec, not a package: prelo add contact-form fetches the spec into your project and your coding agent implements it as plain code you own. Browse the registry at prelo.dev/plugins.

Requirements

Node ≥ 22.5 (node:sqlite). sharp is optional — without it, uploads skip thumbnail generation and originals serve fine.

License

MIT © Prelo contributors. Third-party notices for the bundled studio are in studio-dist/THIRD-PARTY-LICENSES.txt.