posthog-js

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

posthog-js@1.442.0 was published on 2026-10-29. Its manifest declares 10 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All posthog-js versions · Permanent reference to 1.442.0

Package specifications

Version1.442.0
License declaration(Apache-2.0 AND MIT)
Published2026-10-29T09:59:25.744Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count10
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size25896.72 KiB
Published file count762
Package typeNot declared
ES module entrydist/module.mjs
Default entrydist/main.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars635
Repository forks367

Install posthog-js 1.442.0

npm install posthog-js@1.442.0
pnpm add posthog-js@1.442.0
yarn add posthog-js@1.442.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review5/10 — Found 12/22 approved changesets -- score normalized to 5
Maintained10/10 — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
License9/10 — license file detected
Branch-Protection4/10 — branch protection is not maximal on development and all release branches
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy10/10 — security policy file detected
Binary-Artifacts7/10 — binaries present in source code
Pinned-Dependencies8/10 — dependency not pinned by hash detected -- score normalized to 8
Fuzzing10/10 — project is fuzzed
SAST10/10 — SAST tool is run on all commits

Evidence and freshness