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

@authorbot/create

v0.1.54

Published

Guided setup for an Authorbot book project.

Downloads

8,420

Readme

@authorbot/create

Guided setup for an Authorbot book project - a Git-backed editorial control plane and collaboration protocol for serial books.

npx @authorbot/create

Answer three questions and you get a book repository that validates, a live reading site, and - if you want it - a collaboration API where you write chapters in your browser.

Authorbot manages authorship. It does not perform authorship.

What it does

Each stage runs on its own (create-authorbot <stage>), and you can stop after any of them:

| Stage | What you get | |---|---| | doctor | checks Node, git, gh, wrangler and offers to log you in | | book | a book repository - title, address, licence, and the files Authorbot needs | | publish | a live reading site on Cloudflare, verified before it says so | | collaborate | sign-in, annotations, votes, and a work queue on the same address | | agent | a scoped token so a software agent can contribute | | upgrade | moves an existing book to a newer Authorbot, as a pull request |

No chapters are created. A book starts empty on purpose: you write the first chapter in the browser, with a title and a box for prose, and Authorbot writes the identifiers and structure. You should never have to hand-write frontmatter.

What it asks of you

A GitHub account, and for the collaboration stage a Cloudflare account - free tiers cover a book of this size. You bring your own accounts and your own repository; nothing is hosted for you, and there is no service to depend on.

How it treats your machine

  • Nothing destructive without asking, and never a default of yes.
  • Resumable. Progress is journalled, so a failure at step nine does not mean starting at step one.
  • Secrets are never echoed, logged, or written to disk. The GitHub App is created through GitHub's manifest flow, so its credentials go straight into your Worker's secrets - you never see or type them.
  • --dry-run prints the whole plan and changes nothing.
  • Everything it creates in your accounts is listed at the end, with how to remove it.

Documentation

MIT licensed.