Sourcemap Explorer
Stack · npm package

posthog-js

Posthog-js allows you to automatically capture usage and send events to PostHog.

latest 1.372.10· SEE LICENSE IN LICENSE· 1,144 versions publishedView on npm

About

Posthog-js allows you to automatically capture usage and send events to PostHog.

Live mirror of the GitHub README. Updated whenever the repo's default branch changes.

posthoglogo

GitHub contributors PRs Welcome GitHub commit activity GitHub closed issues

Posthog JS

This is a monorepo containing multiple packages to integrate with Posthog using JavaScript!

Documentation

Packages

Contributing

See CONTRIBUTING.md

Quick facts

Latest version1.372.10
LicenseSEE LICENSE IN LICENSE
Authorengineering@posthog.com
Repositorygithub.com/PostHog/posthog-js
Homepageposthog.com/docs/libraries/js
Installnpm install posthog-js
Direct dependencies13

How Sourcemap Explorer detects posthog-js

We catch posthog-js from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/posthog-js/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.

  1. 1

    Confirm the site exposes sourcemaps

    In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment.

  2. 2

    Find the package in the bundle

    Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/posthog-js/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/posthog-js/package.json` gives you the exact installed version.

  3. 3

    Read the version directly from package.json

    Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/posthog-js/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Recent versions

Version
Released
1.0.0
—
1.0.1
—
1.0.2
—
1.0.3
—
1.0.4
—
1.0.5
—
1.0.6
—
1.1.0
—

FAQ

What is posthog-js used for?

Posthog-js allows you to automatically capture usage and send events to PostHog.

How can I tell if a website is using posthog-js?

Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `posthog-js` from two complementary signals: `node_modules/posthog-js/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.

What is the latest version of posthog-js?

1.372.10, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.

Where can I read more?

Project homepage: https://posthog.com/docs/libraries/js. Source code: https://github.com/PostHog/posthog-js. Published on npm: https://www.npmjs.com/package/posthog-js. Licensed as SEE LICENSE IN LICENSE.

Detected by Sourcemap Explorer

When a bundle ships sourcemaps, we read the embedded package.json for posthog-js and report the precise version. Without sourcemaps, an import / require in the page's scripts is enough to flag it.

Install free on Chrome