Is Typesense Still Maintained? Live GitHub Status
On GitHub, the project describes itself as: “Open Source alternative to Algolia + Pinecone and an Easier-to-Use alternative to ElasticSearch ⚡ 🔍 ✨ Fast, typo tolerant, in-memory fuzzy Search Engine for building delightful search experiences”
Short answer: Yes, but development has slowed. Health score 57/100. Checked 18 Oct 2026.
What the numbers say
Typesense’s v31 branch received 31 commits in the last 91 days, against 81 in the same 91 days a year earlier (−62%). That is less than half of last year’s pace, which the index labels “slowing down”. It has 27,002 stars on GitHub.
Typesense usage: downloads and installs
typesense/typesenseDownload and pull counts include automated installs from CI pipelines, containers and mirrors, so they show how widely the software is pulled, not how many people use it. Docker Hub reports an all-time total. Numbers from different registries are not comparable with each other. Sources: Docker Hub, read 18 Oct 2026, 19:52 UTC.
Typesense security practices and adoption
Security practices
OpenSSF Scorecard, an automated review of how the repository is run
- Code review8/10
- Branch protectionn/a
- Dangerous workflow10/10
- Pinned dependencies2/10
- Security policy9/10
All 14 checks
- Maintained10/10
- Packagingn/a
- Token permissions10/10
- Binary artifacts10/10
- OpenSSF Best Practices badge0/10
- License10/10
- Fuzzing0/10
- Signed releasesn/a
- Static analysis (SAST)0/10
Full report, run 12 Oct 2026
Scorecard checks security practices such as code review, branch protection and pinned dependencies; it does not find bugs, and a low score does not mean the software is unsafe. Dependents and download counts show reach, not quality. Sources: OpenSSF Scorecard, GitHub, read 18 Oct 2026, 20:35 UTC.
Health score breakdown
| Part | Points | Based on |
|---|---|---|
| Activity | 19.0 / 35 | 31 commits in the last 91 days (full marks at 600) |
| Trend | 7.7 / 20 | 38% of last year’s pace (full marks at 100%) |
| Recency | 15.0 / 15 | last commit 5 days ago |
| Releases | 4.0 / 10 | latest GitHub release 182 days ago |
| Community | 11.4 / 20 | 25 pull requests merged in the last 91 days (full marks at 300) |
Open issues and pull requests: 911. The score summarises maintenance signals only, not quality or security. How the score works
Typesense: common questions
Is Typesense still maintained?
Yes, but development has slowed. As of 18 October 2026, Typesense received 31 commits in the last 91 days, less than half of its pace a year earlier; the latest commit is from 13 October 2026. Its health score is 57 out of 100.
What is the latest Typesense release?
The latest GitHub release of Typesense is v30.2, published on 19 April 2026.
How many people contribute to Typesense?
GitHub lists 54 contributors for Typesense. 25 pull requests were merged in the last 91 days.
What licence does Typesense use?
GitHub identifies the Typesense licence as GPL-3.0. Read the licence file before commercial use.
Is Typesense secure?
We cannot say whether the code is free of vulnerabilities. What can be measured is how the project is run: the OpenSSF Scorecard gives Typesense 7.2 out of 10 for security practices (run 12 October 2026), covering checks such as code review, branch protection and pinned dependencies. Read the full report and the project’s security policy before relying on it.
How is the health score calculated?
It adds five parts from public GitHub data: commit activity over 91 days (35 points), the trend against the same period last year (20), how recent the last commit is (15), how recent the last release is (10) and merged pull requests (20). Archived projects score 0; a maintenance notice caps the score at 25. It measures maintenance signals only, not code quality or security.
Visitor rating
Have you used Typesense? Rate it:
Ratings come from visitors, not from EvalAITools, and are not part of the health status above. One rating per visitor per tool every 30 days.
Daily snapshots
| Date (UTC) | Stars | Commits, last 91 days | Status |
|---|---|---|---|
| 18 Oct 2026 | 26,996 | 31 | Slowing down |
| 17 Oct 2026 | 26,984 | 37 | Slowing down |
One snapshot is stored per day, starting 16 October 2026. No status change has been recorded for Typesense since then.
Other vector databases
| Tool | Status | Stars | Commits (91d) | vs last year |
|---|---|---|---|---|
| Meilisearch | Active | 59.6k | 353 | −37% |
| Milvus | Active | 46.4k | 651 | +18% |
| Faiss | Active | 41.2k | 164 | +59% |
| Qdrant | Active | 35.1k | 709 | +104% |
| Chroma | Slowing down | 29.5k | 115 | −66% |
| Typesense | Slowing down | 27.0k | 31 | −62% |
| pgvector | Active | 23.4k | 118 | +269% |
| Weaviate | Active | 16.9k | 3,561 | +143% |
| LanceDB | Active | 11.7k | 482 | +219% |
| sqlite-vec | No recent commits | 8.2k | 0 | — |
| Vespa | Active | 7.1k | 1,835 | +28% |
| Marqo | No recent commits | 5.0k | 0 | −100% |
| pgvecto.rs | No recent commits | 2.2k | 0 | — |
Status badge
Show Typesense’s live maintenance status in a README. The badge updates with this page and links back to it.
[](https://evalaitools.com/tools/typesense/)Read next
How this is measured: commits on the repository’s default branch counted through the GitHub API, the last 91 days against the same 91 days a year earlier; archived flag and licence from the repository; README checked daily for maintenance notices. Commit counts measure activity, not quality, and we have not tested this tool ourselves for this page.