A
SwiftInfo
64.8
1,148 stars · MIT
Analytics
Umami leads by 32.6 · decisive
A
64.8
1,148 stars · MIT
B · leads
97.4
40,194 stars · MIT
SwiftInfo versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. SwiftInfo is written mainly in Swift; Umami is written mainly in TypeScript. The composite score is 64.8 for SwiftInfo and 97.4 for Umami.
Umami has 40,194 GitHub stars to SwiftInfo's 1,148, a gap of 39,046 (35.01×). Forks are 58 for SwiftInfo and 8,567 for Umami. On the log scale used inside this pair, adoption is 66 versus 100, and the fork community is 45 versus 100.
Push history: SwiftInfo was last pushed on 18 December 2025 (339 days ago), and Umami was last pushed on 17 November 2026 (5 days ago). Open issues stand at 22 for SwiftInfo (0.019 per star) and 136 for Umami (0.003 per star). Issue-health scores are 84 and 96; activity scores are 36 and 92.
Both SwiftInfo and Umami 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 SwiftInfo (1,148 stars) and Umami (40,194 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: SwiftInfo is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 56 points (36 vs 92), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 97.4 against SwiftInfo at 64.8, a 32.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 | SwiftInfo | Umami |
|---|---|---|
| GitHub stars | 1,148 | 40,194 |
| Forks | 58 | 8,567 |
| Open issues | 22 | 136 |
| Adoption | 66 | 100 |
| Activity | 36 | 92 |
| Community | 45 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 64.8 | 97.4 |
📊 Extract and analyze the evolution of an iOS app's code.
Umami is a small web analytics product with a simple dashboard over page and event data. It is MIT-licensed and is usually chosen when a team wants a short self-hosted setup.
Umami has more GitHub stars: 40,194 versus 1,148 for SwiftInfo. The gap is 39,046 stars.
Umami was pushed more recently: 17 November 2026 versus 18 December 2025 for SwiftInfo. That is 334 days apart.
Yes. This catalog marks both SwiftInfo and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
SwiftInfo 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. Umami 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.
Umami scores 97.4 and SwiftInfo scores 64.8. This page calls that a decisive lead for Umami.