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

@punchline-analytics/analyze

v0.1.0

Published

How much of your site's traffic is AI agents? Analyze a server log export (Vercel, Cloudflare, Apache/Nginx, CSV) offline with Punchline Analytics' classifier: verified operators, impostors, what agents read. Also a Claude Code skill.

Readme

@punchline-analytics/analyze

How much of your site's traffic is AI agents? Point this at a server log export and find out, offline: which operators (OpenAI, Anthropic, Google, Perplexity, …), whether each claim checks out against the operator's published addresses, who's borrowing a known agent's name, what agents read, which assistants sent people, and whether your bot rules turned verified assistants away.

It runs the same classifier and registry as Punchline Analytics, bundled, so it works with no account and no network. Nothing from the export is kept or sent anywhere.

npx @punchline-analytics/analyze access.log --host example.com

Reads, with the format detected:

  • Vercel log drain exports (JSON array or NDJSON with a proxy object per request)
  • Cloudflare Logpush "HTTP requests" NDJSON
  • Apache / Nginx combined access logs (pass --host)
  • CSV / TSV with a header row: address, user agent, path or URL, and optionally host, method, status, referrer, time

Options: --format vercel|cloudflare|combined|csv|json, --host, --rdns (also confirm operators by reverse DNS), --json (counts instead of a report), --top N.

As a Claude Code skill

npx @punchline-analytics/analyze --install-skill

writes .claude/skills/agent-traffic/SKILL.md into the current project. Then, in Claude Code: "analyze my AI agent traffic" and hand it the export. The skill runs this tool and explains the result for the site owner: what kinds of agents came (training crawlers, assistants fetching for a person, agents acting for one), which claims were impostors, and what to change.

Library

import { analyze, parseLogs, renderReport } from "@punchline-analytics/analyze";

const { requests, skipped } = parseLogs(text, { host: "example.com" });
const result = await analyze(requests, { skipped });
console.log(renderReport(result));

What it can and can't see

Logs carry the address, user agent, path, referrer and status. They don't carry Web Bot Auth signatures, the headers every browser sends, or anything from inside the page, so rule R1 (signatures) and R15 (missing browser headers) don't apply, and sessions aren't available. A live install sees all of that; the docs explain the difference: https://punchlineanalytics.com/docs/analyze-logs

MIT.