A · leads
PostHog
94.7
40,849 stars · MIT
Analytics
PostHog leads by 31.6 · decisive
A · leads
94.7
40,849 stars · MIT
B
63.1
2,001 stars · MIT
PostHog versus stacks-cli is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. PostHog is written mainly in Python; stacks-cli is written mainly in JavaScript. The composite score is 94.7 for PostHog and 63.1 for stacks-cli.
PostHog has 40,849 GitHub stars to stacks-cli's 2,001, a gap of 38,848 (20.41×). Forks are 3,696 for PostHog and 70 for stacks-cli. On the log scale used inside this pair, adoption is 100 versus 72, and the fork community is 100 versus 52.
Push history: PostHog was last pushed on 17 November 2026 (0 days ago), and stacks-cli was last pushed on 25 March 2019 (2794 days ago). Open issues stand at 4,463 for PostHog (0.109 per star) and 22 for stacks-cli (0.011 per star). Issue-health scores are 52 and 84; activity scores are 100 and 16.
Both PostHog and stacks-cli are listed as MIT. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both PostHog (40,849 stars) and stacks-cli (2,001 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: PostHog is freemium, stacks-cli is open source.
The lead is split. PostHog is furthest ahead on recent activity (100 to 16), while stacks-cli is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
PostHog finishes ahead at 94.7 against stacks-cli at 63.1, a 31.6 point decisive margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | PostHog | stacks-cli |
|---|---|---|
| GitHub stars | 40,849 | 2,001 |
| Forks | 3,696 | 70 |
| Open issues | 4,463 | 22 |
| Adoption | 100 | 72 |
| Activity | 100 | 16 |
| Community | 100 | 52 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 63.1 |
PostHog is a product-analytics suite: events, funnels, session replay, and feature flags. The core is open source and most teams choose between self-hosting and PostHog Cloud.
📊 Analyze website stack from the terminal 💻
PostHog has more GitHub stars: 40,849 versus 2,001 for stacks-cli. The gap is 38,848 stars.
PostHog was pushed more recently: 17 November 2026 versus 25 March 2019 for stacks-cli. That is 2794 days apart.
Yes. This catalog marks both PostHog and stacks-cli as self-hostable. Confirm each project's deploy docs before you plan a migration.
PostHog is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. stacks-cli is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
PostHog scores 94.7 and stacks-cli scores 63.1. This page calls that a decisive lead for PostHog.