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

@unbrowse/sdk

v11.2.0

Published

TypeScript SDK for Unbrowse 11.2.0: local runtime control, truthful health, and public stats.

Readme

@unbrowse/sdk

TypeScript client for the Unbrowse 11.1.9 local runtime. It can connect to an existing runtime or start the unbrowse binary for the lifetime of your process.

New applications that do not need process control should use the SDK bundled in unbrowse:

import { Unbrowse } from "unbrowse/sdk";

Install

npm install @unbrowse/sdk unbrowse

Start locally

import { Unbrowse } from "@unbrowse/sdk";

const unbrowse = await Unbrowse.local({
  apiKey: process.env.UNBROWSE_API_KEY,
});

try {
  const resolved = await unbrowse.resolve({
    intent: "list tomorrow's events",
    url: "https://calendar.google.com",
  });
  console.log(resolved.result);
} finally {
  await unbrowse.close();
}

Unbrowse.local() reuses a healthy runtime on 127.0.0.1:6969 or starts one when necessary. Use connect(url) when another process owns the runtime and spawn() when you always want an isolated child.

Health and public stats

const live = await unbrowse.liveness();
const ready = await unbrowse.readiness();
const summary = await unbrowse.statsSummary();
const flywheel = await unbrowse.flywheel();

liveness() answers whether the process is up. readiness() includes storage dependency state and returns a typed degraded response when Cloudflare KV is serving as the fallback, rather than throwing on the readiness HTTP 503.

Credits

Metered work is charged to account credits through the normal account API.

const credits = await unbrowse.credits();
console.log(credits.balance_uc / 1_000_000);

An HTTP 402 becomes InsufficientCreditsError. Add credits, then retry the same request. Executes retain their normal idempotency behavior.

Authentication

Pass apiKey to the constructor/factory or set UNBROWSE_API_KEY. Create a key with:

unbrowse register --email [email protected]