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

@analyticstrend/web

v0.5.0

Published

AnalyticsTrend SDK for websites. No cookies, no fingerprinting.

Readme

@analyticstrend/web

Product analytics for websites. No cookies, no fingerprinting, no personal data.

npm install @analyticstrend/web
import { init } from "@analyticstrend/web";

const analytics = init({ writeKey: "wk_your_key_here" });

analytics.track("page_view");

init sends anything left over from a previous visit, and flushes again as the page is leaving.

Single-page applications need one more line. init runs once per document load, so client-side navigation fires nothing and your page views count first loads only. Track route changes yourself.

What is captured

From 0.2.0 the SDK adds a few properties of its own, so that traffic sources and page flow work without your wiring anything up:

| Property | From | | --- | --- | | $referrer | the referring site's hostname, when it is not your own | | $utm_source, $utm_medium, $utm_campaign, $utm_content, $utm_term | the landing URL | | $ref | the ref or source parameter | | $click_id | the name of a gclid, msclkid or fbclid parameter, never its value | | $path | the current path | | $from_path | the previous path, on page views |

Only those parameter names are read. The rest of the query string is never looked at, which matters because query strings routinely carry email addresses and one-time tokens.

To turn it off:

const analytics = init({ writeKey: "wk_your_key_here", autoCapture: false });

Full documentation: https://analyticstrend.com/docs