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

sana-cms

v0.0.1

Published

Self-hosted CMS framework — scaffolds a Next.js project with blog, forms, and docs modules wired to a single REST API.

Readme

sana-cms

Self-hosted CMS framework — scaffolds a Next.js project with blog, forms, and docs modules wired to a single REST API.

Quick start

# Interactive scaffolding (recommended)
npx sana-cms@latest create my-cms

# Or globally
npm install -g sana-cms
sana-cms create my-cms

The interactive flow asks for: project name, template (standalone studio vs embed), modules, database (SQLite local / Postgres), admin credentials, and whether to install + bootstrap immediately.

Non-interactive

npx sana-cms create my-cms \
  --no-interactive \
  --modules blog,forms \
  --db sqlite \
  --email [email protected] \
  --password 'pass1234' \
  --install

Other commands

sana-cms migrate                                       # idempotent schema bootstrap
sana-cms seed --email [email protected] --password ...  # admin + demo project + API key
sana-cms keys --project <id> --scopes blog:*           # issue additional API keys

All runtime commands assume a sana.config.json in the current directory and respect the standard SANA_* env vars (see .env.example after scaffolding).

Deploy

The generated next.config.ts already pins serverExternalPackages: ["better-sqlite3"] so vercel build works. For production, switch the database to Postgres in sana.config.json and set SANA_DB_URL / DATABASE_URL in your hosting provider.

Links

License

MIT