PostHog SDK versions.
The PostHog packages Versyka recognizes on npm and PyPI, their latest releases, and where the breaking changes are documented. Monitoring checks connected repositories against these every day.
Packages we track
| Package | Registry | Latest | Status | Release notes |
|---|---|---|---|---|
posthog-node | npm | 5.57.2 | Maintained | View → |
posthog-js | npm | 1.438.24 | Maintained | View → |
posthog | PyPI | 7.75.11 | Maintained | View → |
Latest versions from the public npm and PyPI registries, checked and refreshed daily.
PostHog SDK questions
What is the latest version of the PostHog SDK?
As of 2026-10-26: posthog-node 5.57.2 on npm; posthog-js 1.438.24 on npm; posthog 7.75.11 on PyPI.
Versions come from the public registries and are refreshed every day.
How do I upgrade the PostHog SDK without breaking my code?
Read the release notes for every major version between yours and the latest, update each call that changed, then run your typecheck, build and tests.
- Versyka's free upgrade check shows which PostHog packages in your package.json or requirements.txt are major versions behind, with the release notes.
- Versyka can do the upgrade for you: it finds every affected PostHog call, rewrites it, runs your own tests and opens a pull request only if they pass.
Does Versyka monitor PostHog SDKs?
Yes. Versyka recognizes posthog-node (npm), posthog-js (npm), posthog (PyPI) in connected repositories and flags them every day when they fall a major version behind or are deprecated.
Behind on PostHog?
Versyka finds every affected PostHog call in your code, rewrites it, runs your tests and opens a pull request.