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

onlyai-pilot

v0.3.2

Published

OnlyAI Pilot — run Pilot's guardrail checks inside Claude Code, Codex, or any terminal. Checks run on OnlyAI's servers; your source is processed in memory and never stored.

Readme

onlyai-pilot

Run OnlyAI Pilot's guardrail checks inside Claude Code, Codex, Cursor, or any terminal. Pilot flags known drift/bug classes (optimistic state, hydration mismatches, unsafe long-jobs, silent write failures, …) — with more review lenses (security, architecture, …) on the way — and returns actionable findings with fixes.

How it runs: the checks run on OnlyAI's servers. The CLI collects the relevant source files from your repo (limited to app / lib / components / src / pages, no node_modules, no .env, size-capped) and sends them over TLS. Your code is processed in memory to produce your findings and is never stored, logged, or used to train anything — it is discarded the moment your results return. Only anonymous, code-free failure patterns (which rule fired + the outcome) are retained to improve Pilot, and only if you leave fleet learning on.

Requires an active OnlyAI Pro plan. Zero dependencies (Node 18+).

Install

npm i -g onlyai-pilot

Use

pilot login <token>     # get a token at onlyaiapp.com/settings → "Pilot in your terminal"
pilot check             # audit the current repo
pilot config telemetry off   # opt out of anonymous fleet learning
pilot help

Tip: add a line to your project's CLAUDE.md (Claude Code) / AGENTS.md (Codex) — "before deploying, run pilot check and fix any blocking findings" — and your AI agent will run it for you.

Config is stored at ~/.onlyai/pilot.json. Override the API base with --api <url> or ONLYAI_API.

License

© OnlyAI (Academy of AI). Proprietary — all rights reserved; requires an active Pro plan. The guardrail rules, prompts, and catalogs run only on OnlyAI's servers and are not licensed to you. See LICENSE.