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

@echoranked/tracker

v0.1.1

Published

Server-side AI crawler tracking and the EchoRanked visitor snippet

Readme

@echoranked/tracker

Server-side AI crawler tracking for EchoRanked, plus the cookieless visitor snippet.

AI crawlers mostly request raw HTML and never run your frontend JavaScript, so a browser snippet cannot see them. This package reports those requests from your server instead. EchoRanked classifies the crawler, verifies its source IP against the operator's published ranges, and shows what each bot fetched — and what it got back.

npm install @echoranked/tracker

Generate an ingest key under Project settings → Connections, keep it in a server-side environment variable, then install whichever adapter matches your stack.

Cloudflare Workers, Hono, Deno, Bun (recommended)

Wrapping the handler is the only shape that sees the response, so it is the only one that can record the status a crawler received.

import { withCrawlerTracking } from "@echoranked/tracker/fetch";

export default {
  fetch: withCrawlerTracking(handler, {
    endpoint: "https://app.echoranked.com/api/crawlers/collect",
    ingestKey: env.ECHORANKED_INGEST_KEY,
  }),
};

Express / Node

import { crawlerMiddleware } from "@echoranked/tracker/node";

app.use(
  crawlerMiddleware({
    endpoint: "https://app.echoranked.com/api/crawlers/collect",
    ingestKey: process.env.ECHORANKED_INGEST_KEY!,
  }),
);

Next.js middleware

Middleware runs before the response exists, so it reports the path, host and referrer but no status. Wrap your route handlers with /fetch as well if you want to see which pages return errors to crawlers.

import { NextResponse } from "next/server";
import { crawlerMiddleware } from "@echoranked/tracker/next";

const track = crawlerMiddleware({
  endpoint: "https://app.echoranked.com/api/crawlers/collect",
  ingestKey: process.env.ECHORANKED_INGEST_KEY!,
});

export function middleware(request, event) {
  track(request, event);
  return NextResponse.next();
}

Any other backend

One POST per batch, up to 50 events:

POST /api/crawlers/collect
Authorization: Bearer <ingest key>
Content-Type: application/json

{"events":[{"ua":"…","path":"/pricing","ip":"…","status":200,"host":"example.com"}]}

What is sent, and what is not

Asset requests (/_next/*, CSS, images, fonts) are filtered out before anything is posted: they are not page fetches, and counting them would make every number larger and less true. robots.txt, llms.txt, llms-full.txt and sitemaps are always reported — a crawler reading them is the signal you published them for.

Nothing about your human visitors is sent, no cookies are set, and the IP is used only to verify the crawler against its operator's published ranges.