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

api-profiler

v1.0.0

Published

Terminal client for api-performance-profiler: route table, recordings and load runs without VS Code.

Downloads

311

Readme

api-profiler

Terminal view of an app running @api-profiler/express: a live route table, recordings, and load runs — no VS Code needed. Zero dependencies.

npm install @api-profiler/express   # in the app, then app.use(profiler())
npx api-profiler                    # in another terminal
api-profiler · app http://127.0.0.1:4780 · v0.1.0 · 14:32:10

Observed traffic
    route            count  avg      max      errors  req/s  when
🟢  GET /users/:id   12     1.7ms    8.9ms    0%      2.4    live
🟡  GET /slow        3      202.1ms  202.5ms  0%      --     40s ago

Load tests
🟢  GET /users/:id   10694  0.1ms    1.3ms    0%      3553   load · 2 min ago

Commands

api-profiler                     live table, refreshed every second (Ctrl-C to stop)
api-profiler routes              routes seen by the app and whether each has a recording
api-profiler stats               per-route figures for the last window (observed and load)
api-profiler load-results        results of past load runs
api-profiler clear               forget all metrics, recordings and load results
api-profiler run GET /users/:id  replay the recorded request under load and report

--port <n>          channel port the app opened (default 4780)
--json              raw JSON instead of a table
--once              live mode: print one frame and exit
--fast <ms>         🟢 below this average (default 200)
--warn <ms>         🟡 below this average, 🔴 from here (default 500)
--connections <n>   run: concurrent connections (default 10)
--duration <s>      run: seconds (default 5)
--target <url>      run: override the recorded origin (localhost only)

-- for requests per second means fewer than 10 samples: a number that was not measured is never shown. A route that goes quiet keeps its last figures, dimmed, with their age.

The CLI only talks to the app's local channel on 127.0.0.1; it never opens a port of its own and never sees a raw recording — the app masks them first.

Licence

AGPL-3.0-only. Source and issues: https://github.com/Nahid625/api-performance-profiler