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

@signalor/cli

v0.1.0

Published

Signalor CLI — scaffold @signalor/nextjs into your Next.js app in 30 seconds.

Readme

@signalor/cli

Zero-config bootstrap for @signalor/nextjs. Drops middleware, llms.txt route, sitemap, postbuild hook, and your API key into an existing Next.js app in 30 seconds.

Quick start

Inside your Next.js project's root directory:

npx @signalor/cli init

That's it. The CLI will:

  1. Detect your project (Next.js + package manager).
  2. Ask for your Signalor API key (skippable — you can wire it later).
  3. Install @signalor/nextjs using whichever package manager you use (pnpm / yarn / npm / bun).
  4. Scaffold four files (never overwriting existing ones):
    • src/proxy.ts on Next.js 16+ / src/middleware.ts on 14-15 — AI-crawler detection
    • app/llms.txt/route.ts — auto-generated llms.txt
    • app/sitemap.ts — Signalor sitemap helper
    • patches package.json scripts.postbuild to run signalor-deploy
  5. Write SIGNALOR_API_KEY to .env.local (if you provided a key).
  6. Print a summary + manual next-steps for <SignalorSchema /> in your root layout.

What it won't do

  • Overwrite existing files. If you already have proxy.ts/middleware.ts, app/llms.txt/route.ts, or app/sitemap.ts, the CLI leaves them alone and prints the snippet you should add manually.
  • Touch your git state. No commits, no branches. Review the diff yourself.
  • Run on non-Next.js apps. It bails out if next isn't in package.json.

Subcommands

| Command | What it does | | ------------------ | ---------------------------------------------- | | signalor init | Bootstrap @signalor/nextjs in this project | | signalor --help | Show usage | | signalor --version | Print the installed version |

More to come (signalor analyze, signalor login).

Get an API key

Mint one at signalor.ai → Settings → Developers. Per-org, revocable any time, shown once on creation.

License

MIT