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

@termind/node

v1.0.1

Published

Termind analytics for Node, Bun and edge runtimes. Server-side events, revenue and AI crawler tracking.

Readme

@termind/node

Termind for your server. Node 18+, Bun and edge runtimes.

npm install @termind/node
import { createTermindServer } from "@termind/node";

const termind = createTermindServer({ apiKey: process.env.TERMIND_API_KEY! });

termind.track("trial_started", { personId: "user_123" }, { plan: "pro" });

await termind.revenue({
  personId: "user_123",
  amountMinor: 4900,   // whole cents, never 49.00
  currency: "EUR",
  plan: "Growth",
});

await termind.flush();   // serverless functions exit fast

Three things only a server can do honestly

Events an ad blocker cannot eat. A browser can be blocked; your handler cannot.

Revenue reported from the code that took the payment. The number is the number.

AI crawler tracking. Crawlers fetch HTML and leave without running any JavaScript, so no browser SDK will ever see one.

// middleware.ts
await termind.crawl({
  path: url.pathname,
  userAgent: request.headers.get("user-agent"),
  // Forward the IP so the claim can be verified. A user-agent is a string
  // anyone can set; without an address it cannot be confirmed.
  ip: request.headers.get("x-forwarded-for")?.split(",")[0] ?? null,
});

The server key starts with sk_ and must never reach a browser. The publishable pk_ key is the one that is safe in public HTML.

Identity is passed per call rather than held on the instance, because a server handles many people at once and an ambient "current user" is a race condition waiting for its first concurrent request.

Docs: https://www.termind.tech/docs/sdks