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

vibex-sh

v1.0.0

Published

Zero-config observability CLI - pipe logs and visualize instantly

Downloads

3,032

Readme

vibex CLI

Zero-config observability CLI - pipe logs and visualize instantly.

Quick Start

# Production (default)
echo '{"cpu": 45, "memory": 78}' | vibex

Installation

npm install -g vibex-sh

Usage

Pipe any output to vibex:

# JSON logs
echo '{"cpu": 45, "memory": 78}' | vibex

# Script output
python script.py | vibex
node server.js | vibex
docker logs -f | vibex

# Reuse session
echo '{"more": "data"}' | vibex --session-id vibex-abc123

Options

| Flag | Description | Example | |------|-------------|---------| | -s, --session-id <id> | Reuse existing session | vibex --session-id vibex-abc123 | | --web <url> | Web server URL | vibex --web https://vibex.sh | | --socket <url> | Socket server URL | vibex --socket wss://ingest.vibex.sh | | --server <url> | Shorthand for --web (auto-derives socket) | vibex --server https://vibex.sh |

Server Configuration

The CLI automatically derives the socket URL from the web URL, but you can override it:

# Production (auto-derives socket URL)
vibex --server https://vibex.sh

# Custom domain
vibex --web https://staging.vibex.sh --socket wss://ingest-staging.vibex.sh

Priority Order

  1. Flags (--web, --socket, --server)
  2. Environment variables (VIBEX_WEB_URL, VIBEX_SOCKET_URL)
  3. Production defaults (https://vibex.sh, wss://ingest.vibex.sh)

Environment Variables

export VIBEX_WEB_URL=https://vibex.sh
export VIBEX_SOCKET_URL=wss://ingest.vibex.sh

Examples

# Production (default)
echo '{"data": 123}' | vibex

# Custom web server, auto socket
echo '{"data": 123}' | vibex --server https://vibex.sh

# Staging
echo '{"data": 123}' | vibex --server https://staging.vibex.sh

License

MIT