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

@nineup/node

v0.1.2

Published

Official Node.js SDK for Nineup — deep health checks, heartbeats, and events for your services.

Readme

@nineup/node

Official Node.js SDK for Nineup — deep health checks, heartbeats, and events.

npm install @nineup/node

Quickstart

import { createNineup } from "@nineup/node";
import { drizzleAdapter, redisAdapter, httpAdapter } from "@nineup/node/adapters";

const nineup = createNineup({
    apiKey: process.env.NINEUP_API_KEY,
    monitorId: process.env.NINEUP_MONITOR_ID,
});

nineup.check("postgres-prod", drizzleAdapter(db));
nineup.check("redis-shared", redisAdapter(redis));
nineup.check("stripe", httpAdapter("https://api.stripe.com/healthz"));

// Expose health at any HTTP route:
// (for Next.js use @nineup/next instead)
http.createServer(nineup.httpHandler()).listen(3000);

What this does — and only this

Three primitives, by design:

  1. Checks — declarative health probes for dependencies.
  2. Heartbeats — wrap things Nineup can't poll (cron, ETL).
  3. Events — discrete annotations (deploy markers, custom signals).

No automatic error capture, no tracing, no metrics, no logs. Use the right tool for those.

Heartbeats

await nineup.heartbeat(process.env.NINEUP_HEARTBEAT_TOKEN!, async () => {
    await runNightlyBackup();
});

If the function throws, the SDK reports status: "fail" with the message and duration, then re-throws.

Events

await nineup.event({
    type: "deploy",
    message: "Shipped v1.2.4",
    metadata: { commit: process.env.VERCEL_GIT_COMMIT_SHA },
});

Adapters

Adapters are just functions matching the CheckFn signature. Ship-with:

  • httpAdapter(url) — generic external probe
  • drizzleAdapter(db) — Drizzle ORM
  • postgresAdapter(client)pg, postgres-js
  • redisAdapter(client)ioredis, node-redis

Writing your own is just a function:

nineup.check("queue", async () => {
    const depth = await queue.depth();
    if (depth > 1000) return { status: "warn", message: `depth=${depth}` };
    return true;
});

Topology

When multiple of your services emit a check with the same name (e.g. postgres-prod), Nineup automatically draws an edge in your account's dependency graph. One failed shared dep → one incident covering all affected services. No extra config beyond consistent naming.

License

MIT