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

@vayo-hq/server

v0.1.1-beta.3

Published

REST API + Socket.IO gateway + static UI hosting. Every mutating route is role-checked server-side (docs/05-security.md).

Readme

@vayo-hq/server

The REST API + Socket.IO realtime gateway + static docs-UI host for Vayo. This is what vayo serve runs standalone — but you can also mount it directly inside your own Express app.

import { createServer } from "@vayo-hq/server";
import { createAdapter } from "@vayo-hq/db-mongo";

const db = createAdapter(process.env.VAYO_MONGO_URI);
const { httpServer } = createServer({ db, mountPath: "/vayo" });
httpServer.listen(4100);

Two auth modes:

  • Standalone (default) — Vayo manages its own team members, invites, and sessions. vayo create-owner creates the first login; everyone after that is invited in-app.
  • Delegated — pass authMiddleware to validate your own app's existing session/JWT instead; Vayo never sees a second set of passwords.

Every mutating route re-reads the caller's current role from your database on every request and is role-checked server-side — a hidden UI button is never the only thing standing between a viewer and an edit.

Serves the built @vayo-hq/ui React app at mountPath automatically once it's installed alongside this package.

Pass your own httpServer to mount Vayo into the same process/port as your real API, instead of running it as a separate standalone server:

const { app: vayoApp, httpServer } = createServer({ db, mountPath: "/docs", httpServer: myHttpServer });
myExpressApp.use(vayoApp);

Most people run this via vayo serve — see @vayo-hq/cli. To mount it yourself instead: npm install @vayo-hq/server@beta.

License

MIT