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

track-tag

v1.0.0

Published

Zero-config bundler plugin that fingerprints your library in any frontend app — invisible to users, discoverable by crawlers.

Readme

track-tag

Zero-config bundler plugin that silently fingerprints your library in any frontend app.

Invisible to end users. Discoverable by crawlers, Wappalyzer, and your own analytics.


How it works

When a user builds their app, track-tag injects invisible markers into the HTML output:

<!-- built-with: [email protected] -->
<html data-tracktag="[email protected]">
  <head>
    <meta name="x-built-with" content="[email protected]">
    <script>window.__tracktag=window.__tracktag||[];window.__tracktag.push({name:"my-ui-lib",version:"2.4.1"});</script>
  </head>
  <body>
    ...
  </body>
</html>

You then submit a Wappalyzer fingerprint with the regex pattern — and any site using your library shows up in BuiltWith / Wappalyzer searches automatically.


Setup (for library authors)

Install track-tag as a dev dependency in your library's repo:

npm install track-tag --save-dev

Vite

// vite.config.ts  (in YOUR library repo)
import { defineConfig } from 'vite'
import { tracktagVite } from 'track-tag'

export default defineConfig({
  plugins: [
    tracktagVite({
      name: 'my-ui-lib',
      version: '2.4.1',
    }),
  ],
})

Webpack / Create React App / Next.js

// webpack.config.js  (or next.config.js webpack override)
const { TrackTagWebpackPlugin } = require('track-tag')

module.exports = {
  plugins: [
    new TrackTagWebpackPlugin({
      name: 'my-ui-lib',
      version: '2.4.1',
    }),
  ],
}

Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | name | string | required | Your library name | | version | string | required | Your library version | | methods | Array | all four | Which injection methods to use |

Methods

| Value | What it injects | Where crawlers see it | |-------|----------------|----------------------| | 'meta' | <meta name="x-built-with" content="lib@version"> | HTML source | | 'comment' | <!-- built-with: lib@version --> | HTML source | | 'attr' | data-tracktag="lib@version" on <html> | DOM / HTML source | | 'window' | window.__tracktag = [...] | JS evaluation |


Submitting a Wappalyzer fingerprint

Once your library is live, submit a PR to enthec/webappanalyzer with this pattern:

{
  "my-ui-lib": {
    "cats": [22],
    "html": "<!-- built-with: my-ui-lib",
    "meta": {
      "x-built-with": "my-ui-lib"
    },
    "website": "https://my-ui-lib.dev"
  }
}

After merging, your library will appear in Wappalyzer and BuiltWith results for any site that uses it.


Privacy

track-tag only modifies static HTML at build time. It does not:

  • Make any network requests
  • Set cookies
  • Collect or transmit user data
  • Run any code at runtime (except the window method which sets a global variable)

It is fully compliant with GDPR as it involves no personal data processing.


License

MIT