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

owlservable

v0.2.11

Published

Minimalist Observability Platform. Zero config, zero dependencies.

Readme

owlservable

One line. See every API call your app makes.

import 'owlservable/auto'

Open http://localhost:4321 and watch requests arrive in real time.

No config. No dependencies. No build step. ~400 lines of vanilla Node.js.


Install

npm install owlservable

Usage

Drop one import at the top of your entry file:

import 'owlservable/auto'

// ... rest of your app

Every fetch(), http.request(), and https.request() your app makes will appear in the dashboard instantly.

CJS projects (TypeScript compiled to CommonJS, Firebase Functions, etc.) — the same import works, Node resolves the right wrapper automatically:

import 'owlservable/auto'  // or require('owlservable/auto')

Manual init

import { init } from 'owlservable'

init({
  port: 4321,       // default: 4321
  dashboard: true,  // default: true
  logging: false,   // log to console, default: false
})

Dashboard

  • Live request log — method, status, latency, URL
  • AI token counts — including streaming
  • Optional 1h / 24h / 7d logs + clear logs

How it works

On import, owlservable monkey-patches globalThis.fetch, node:http, and node:https. Every outbound call passes through a thin wrapper that records timing and metadata, then forwards unchanged. A plain http.createServer serves one HTML file. Real-time updates arrive via Server-Sent Events

Requirements

  • Node.js 18+
  • Zero runtime dependencies

Security

Development only. owlservable exits immediately when NODE_ENV=production. Keep it in devDependencies and never bundle it into a production build.

  • Dashboard binds to 127.0.0.1 only — not accessible over a network
  • No authentication on the dashboard port
  • Request bodies up to 32 KB are captured in memory — avoid secrets in request bodies
  • Authorization headers are not captured
  • API keys passed as query params will appear in the URL log
  • When persistence is enabled, .owlservable/log.ndjson contains full request data — treat it as sensitive

License

MIT