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

@n50/omnisentinel

v0.1.0-alpha.0

Published

Portable, framework-agnostic runtime observability + survival mode for any Node.js/Python process. Drop-in self-healing.

Readme

@alef/omnisentinel

Portable runtime observability + graceful degradation for any Node.js process.

Decoupled from ALEF core. Drop into any Node/Python service. Same architectural benefits without the framework lock-in.

Why

Most services have one of two visible states: "running" or "dead". You discover dead-state through alerts AFTER the failure already hurt the user. OmniSentinel adds a middle layer:

  • Per-agent sidecar heartbeats — append-only JSONL, the SOLE evidence when a process crashes
  • Fleet-level monitor — classifies each agent as FRESH/WARM/STALE/DEAD/GHOST/STOPPED
  • Survival mode — when resources or upstream degrade, automatically reduce load instead of crashing

The contract is JSON-Lines per agent + a single status file. Python and other languages can write to the same JSONL files via the documented schema.

Install

npm install @alef/omnisentinel

Use — single-agent heartbeat

import { sentinel } from "@alef/omnisentinel";

const s = sentinel({ name: "my-service", dir: "./meta/sentinel" });
s.boot("v1.0.0 starting");
s.heartbeat("processing payment", { state: "active", confidence_score: 0.95 });
s.startTimer(60_000);  // periodic heartbeat
process.on("SIGINT", () => { s.shutdown("SIGINT"); process.exit(0); });

Use — fleet monitor

import { runMonitor } from "@alef/omnisentinel/monitor";

runMonitor({
  dir: "./meta/sentinel",
  statusFile: "./meta/sentinel_status.json",
  tickSec: 30,
  knownAgents: ["api-server", "worker-1"],
});

Use — survival mode

import { runSurvival } from "@alef/omnisentinel/survival";

runSurvival({
  flagFile: "./automation/SURVIVAL_MODE_ACTIVE",
  memMinMb: 200,
  upstreamHealthFn: (sig) => checkLLM() ? 0 : 1.0,
});

Loops read the flag at top of iteration:

if (existsSync("./automation/SURVIVAL_MODE_ACTIVE")) {
  await sleep(cooldownMs * 10);
  continue;
}

License

CC-BY-4.0. See Doctrine #32 — The Sentinel Rule for architectural rationale.