@posthog/clinpm
- latest 0.19.3
- last known licence MIT
- stars 40,741
- assessment attempted today
- GitHub evidence observed today
- registry checked 18 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Maintenance trends
Loading historical repository activity…
Signals · last 12 checks
Commits 90d
100
Open issues
3347
Unanswered
1896
Contributors
37
What the project says about itself
- Build provenance — the latest release, 0.19.3, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node >=14.14. Source: the registry.
- Publishers on the registry — 21. Source: the registry.
- Open milestones — New engine is the default 1/1 done; Revenue Analytics Open Beta (due 2025-08-25) 12/12 done; modeling q2 (due 2026-07-01) 0/3 done; Redesign authentication and onboarding flows (due 2026-09-30) 5/8 done. Source: the repository's milestones.
- OpenSSF Scorecard — 4.6 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 10 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-11 | first verdict: active |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@posthog/cli)Watch it
Get told when @posthog/cli changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.