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

oatbox

v0.1.1

Published

Install the Oatbox widget in your web app with one command.

Downloads

27

Readme

oatbox CLI

Install the Oatbox widget in your web app with one command.

Quick start

npx oatbox@latest init YOUR_AGENT_ID

Replace YOUR_AGENT_ID with the agent ID shown in your Oatbox dashboard at /admin/install.

What it does

  1. Reads your package.json to detect your framework automatically.
  2. Locates the right file (app/layout.tsx, index.html, nuxt.config.ts, etc.).
  3. Inserts the Oatbox <script> tag idempotently — running it twice won't duplicate the tag.
  4. Prints a confirmation with the file path changed.

Supported frameworks

| Framework | Target file edited | |------------|---------------------------| | Next.js | app/layout.tsx | | React | index.html / public/index.html | | Vue | index.html | | Nuxt | nuxt.config.ts | | Angular | src/index.html | | SvelteKit | src/app.html | | Svelte | index.html | | Plain HTML | index.html (auto-detected) |

Options

--origin=<url>        Widget server origin
                      (default: https://app.oatbox.ai)
--dry-run             Preview changes without writing files
--force               Skip git-dirty check
--framework=<name>    Override framework detection

Examples

# Auto-detect and install
npx oatbox@latest init cmnwd9d5w0000aw9kjolkro60

# Preview what would change
npx oatbox@latest init cmnwd9d5w0000aw9kjolkro60 --dry-run

# Override framework detection
npx oatbox@latest init cmnwd9d5w0000aw9kjolkro60 --framework=react

# Self-hosted Oatbox instance
npx oatbox@latest init cmnwd9d5w0000aw9kjolkro60 --origin=https://my.oatbox.instance

What this does NOT do

  • Install or update npm dependencies
  • Start your dev server
  • Commit or push any changes to git
  • Modify any file other than the single template/entry file listed above

Manual installation

If the CLI can't detect your setup, add this to your HTML <body> manually:

<script src="https://app.oatbox.ai/widget/YOUR_AGENT_ID" async></script>

For Next.js, use the next/script component:

import Script from "next/script"

// Inside your layout <body>:
<Script src="https://app.oatbox.ai/widget/YOUR_AGENT_ID" strategy="afterInteractive" />

More

Full installation docs: https://app.oatbox.ai/admin/install

Security

This CLI has zero install-time scripts and zero runtime dependencies. It only modifies one file per run (the one your framework's docs point to). Use --dry-run to preview before any change.

Report security issues privately to [email protected] — see the Security Policy.

Changelog

See CHANGELOG.md.

License

MIT