Trending Categories Repositories Insights Dependencies Withheld

Trending Categories Repositories Insights Dependencies Withheld

Trending repositories

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

Period

Sort order

Topics: change-data-capture

Topics

Search topics

No listed topic matches. Press Enter to filter by “”.

Category

Filters

Apply

Filters

Primary language

License

Total stars

Last push

Created

Archived

Clear all filters

5 repositories by Attention Score · Oct 27, 2026 – Nov 2, 2026 (UTC)

Topic: change-data-capture

1.cocoindex-io / cocoindex

Incremental engine for long horizon agents 🌟 Star if you like it!

ai
change-data-capture
data-indexing
etl
indexing
python
+14 more

Rust APACHE-2.012K total924 forks

+51 stars

from 11,754 · score 3.95

2.debezium / debezium

Change data capture for a variety of databases. Please log issues at https://github.com/debezium/dbz/issues.

change-data-capture
kafka-connect
apache-kafka
debezium
cdc
database
+5 more

Java APACHE-2.013K total3.1K forks

+32 stars

from 13,270 · score 3.50

3.airbytehq / airbyte

Open-source data movement for ELT pipelines and AI agents — from APIs, databases & files to warehouses, lakes, and AI applications. Both self-hosted and Cloud.

data
pipeline
data-analysis
data-engineering
java
python
+14 more

Python Other license22K total5.4K forks

+31 stars

from 22,264 · score 3.47

4.apache / seatunnel

SeaTunnel is a multimodal, high-performance, distributed, massive data integration tool.

data-integration
high-performance
offline
real-time
apache
batch
+8 more

Java APACHE-2.09.8K total2.5K forks

+21 stars

from 9,758 · score 3.09

5.estuary / flow

🌊 Continuously synchronize the systems where your data lives, to the systems where you _want_ it to live, by managing your data flows with Estuary. 🌊

change-data-capture
data
data-collection
data-engineering
data-integration
data-pipeline
+2 more

Rust Other license987 total102 forks

+2 stars

from 985 · score 1.10

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 a repository's first Observation. A longer window needs more days of Observations first. A repository younger than the window is not ranked in it.

The filters narrow 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 Category holds the repositories that its published rules match; see Categories.

Repositories enter the index from the Seed Dataset or by gaining stars faster than the published admission threshold, whatever their size. Admission is permanent, so an archived repository can still rank.

Browse the Repository Index

Trending Categories Repositories Insights Dependencies Withheld Withholding Rule Privacy Send feedback