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

@pegma/health

v0.2.0

Published

Composable health probes and HTTP responses for Pegma hosts.

Readme

@pegma/health

Composable health probes and HTTP responses for Pegma hosts.

[!IMPORTANT] Pegma is in early 0.x development. This package's public API is unstable.

import {
  createProcessCheck,
  createStorePingCheck,
  runHealthChecks,
  toHealthResponse,
  healthProbeCollection,
} from "@pegma/health";
import { createMemoryStore } from "@pegma/storage-core";

const store = createMemoryStore();
const result = await runHealthChecks({
  service: "my-api",
  checks: [
    createProcessCheck(),
    createStorePingCheck({
      store,
      collection: healthProbeCollection,
    }),
  ],
});
const { status, body } = toHealthResponse(result);

Hosts register checks at the composition root. This package never creates a storage adapter and never invents domain collections for you — pass an injected Store and a collection definition you own (or use the exported healthProbeCollection convenience definition).

Check names must be unique. A check that throws is reported as { status: "fail", detail: { reason: "check_threw" } } and the error text is logged through the injected Logger only, never placed in the public body. A check must settle, though: runHealthChecks imposes no deadline of its own, so bound your own I/O the way createStorePingCheck bounds its timeoutMs.

createStorePingCheck writes and reads on every call, so a host serving it on a public route SHOULD rate limit or briefly cache that route — see docs/MONITORING.md.