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: workflow-engine

Topics

Search topics

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

Category

Filters (1)

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)

Language: Java
Topic: workflow-engine
Clear all

1.conductor-oss / conductor

Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents

distributed-systems
grpc
java
javascript
microservice-orchestration
orchestration-engine
+8 more

Java APACHE-2.032K total1.1K forks

+16 stars

from 32,384 · score 2.83

2.flowable / flowable-engine

A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.

bpmn
java
workflow
workflow-engine

Java APACHE-2.09.6K total2.9K forks

+13 stars

from 9,619 · score 2.64

3.camunda / camunda

Agentic Orchestration Platform

microservices
orchestration-framework
workflow-engine
java
bpmn
workflow
+1 more

Java No license4.3K total840 forks

+6 stars

from 4,339 · score 1.95

4.azkaban / azkaban

Azkaban workflow manager.

workflow-engine
azkaban
scheduling
hacktoberfest

Java APACHE-2.04.5K total1.6K forks

+1 stars

from 4,511 · score 0.69

5.littlehorse-enterprises / littlehorse

LittleHorse Server: Business-as-Code Platform for Microservices, Workflows, and Agents

microservices
workflow-engine
orchestration
apache-kafka
event-driven-architecture
kafka-streams
+1 more

Java AGPL-3.0401 total39 forks

+1 stars

from 400 · score 0.69

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