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

@hyperwatch/hyperwatch

v5.3.3

Published

Open Source HTTP Traffic Manager

Readme

NPM version Build Status

Hyperwatch is a flexible access log processor that helps operators analyze HTTP traffic reaching their infrastructure.

Hyperwatch is built on a real-time stream processor handling logs from inputs of any type:

  • CDNs (Cloudfront, Cloudflare, Akamai, ...)
  • Load Balancers (ELB)
  • Reverse Proxies (Nginx, Haproxy, ...)
  • Web Servers (Nginx, Apache, ...)
  • Applications (Node, Ruby, PHP, ...)

Install

Make sure you have Node.js version >= 24.

We recommend using nvm: nvm install && nvm use.

git clone https://github.com/hyperwatch/hyperwatch.git
cd hyperwatch
npm install

Start

npm start

It's loading the default configuration, it's the same as:

npm start config/default

Configure

The first thing you might want is configuring inputs to connect Hyperwatch to your traffic sources and convert it in the proper format.

In order to do this, you need to create a new configuration file such as config/custom.js.

See Input Configuration for the list of available input types and how to configure them.

Modules (live log streams, User-Agent parsing, GeoIP, aggregations, …) and a few constants are configured with a .hyperwatchrc file. Only the status module is active by default. To learn more, head to Global Configuration.

To tag requests from listed IPs and User-Agents, and sync those lists with Cloudflare custom rules, see Firewall.

Start with custom configuration

npm start config/custom

The Hyperwatch API and WebSocket will be served from port 3000 by default. Open http://localhost:3000/ to check the status of your inputs. The top navigation links to the addresses, identities and logs pages of the active modules, and to /pipeline, which shows how the pipeline is set up: inputs, nodes, and what runs on each. An application's own aggregators join it with app.api.registerAggregator(name, aggregator, { nav: true }), before logs, or { nav: { after: 'logs' } } (before or after any registered section; last when that section isn't registered).

You can change that using an environment variable:

PORT=80 npm start config/custom

Tutorials

License

Apache License, version 2