Trending repositories

Ranked by Attention Score: stars gained over the last 180 complete days

Period

Sort order

Tag

Filters (1)

Apply

Filters

Primary language

License

Total stars

Last push

Created

Archived

Clear all filters

6 repositories by Attention Score · May 8, 2026 – Nov 3, 2026 (UTC)

Language: Rust
Tag: Search engine
Clear all

1.meilisearch / meilisearch

A lightning-fast search engine API bringing AI-powered hybrid search to your sites and applications.

search-engine
typo-tolerance
site-search
database
enterprise-search
search
+14 more

Rust Other license60K total2.8K forks

+2,681 stars

from 57,089 · score 7.89

2.quickwit-oss / tantivy

Tantivy is a full-text search engine library inspired by Apache Lucene and written in Rust

search-engine
rust

Rust MIT16K total1K forks

+1,321 stars

from 15,073 · score 7.19

3.paradedb / paradedb

One Postgres for your application data, full-text search, vector retrieval, and aggregations. Home of the pg_search extension.

sparse-vector
hybrid-search
bm25
full-text-search
analytics
olap
+14 more

Rust AGPL-3.09.5K total496 forks

+782 stars

from 8,692 · score 6.66

4.quickwit-oss / quickwit

Cloud-native OSS search engine for observability

rust
log-management
logs
tantivy
cloud-native
open-source
+4 more

Rust APACHE-2.012K total625 forks

+658 stars

from 11,106 · score 6.49

5.valeriansaliou / sonic

🦔 Fast, lightweight & schema-less search backend. An alternative to Elasticsearch that runs on a few MBs of RAM.

rust
infrastructure
search
index
graph
database
+4 more

Rust MPL-2.021K total621 forks

+268 stars

from 21,109 · score 5.59

6.tinysearch / tinysearch

🔍 Tiny, full-text search engine for static websites built with Rust and Wasm

bloom-filter
static-site
search-engine
wasm
rust
lunrjs
+2 more

Rust APACHE-2.03K total94 forks

+56 stars

from 2,923 · score 4.04

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before the first daily record that AwesomeRepos made for the repository. A longer window needs more of these daily records first. A repository younger than the window does not rank in it.

The filters select from the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Tag holds the repositories that have it. See Tags.

Repositories enter the index from the starting dataset of the index, or by gaining stars faster than the published admission threshold, whatever their size. A repository stays in the index after it enters. Thus an archived repository can still rank.

Browse the Repository Index