RepoPilot

kestra-io/kestra vs water8394/flink-recommandsystem-demo

kestra-io/kestra shows stronger signals overall

As of June 2026, kestra shows healthier maintenance signals than flink-recommandsystem-demo. kestra rates Healthy overall while flink-recommandsystem-demo rates Concerns. kestra last saw a commit 1 month ago with 19+ active contributors, while flink-recommandsystem-demo last saw a commit 2 years ago with 2+ active contributors. Neither has known critical or high-severity CVEs in its dependency tree.

Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.

kestra-io/kestra

Healthy

Healthy across the board

HealthyDependency

Permissive license, no critical CVEs, actively maintained — safe to depend on.

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Last commit today
  • 19 active contributors
  • Distributed ownership (top contributor 26% of recent commits)
  • Apache-2.0 licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

water8394/flink-recommandsystem-demo

Concerns

Stale and unlicensed — last commit 2y ago

ConcernsDependency

no license — legally unclear; last commit was 2y ago…

ConcernsFork & modify

no license — can't legally use code; no CI workflows detected…

HealthyLearn from

Documented and popular — useful reference codebase to read through.

ConcernsDeploy as-is

no license — can't legally use code; last commit was 2y ago…

  • Stale — last commit 2y ago
  • Small team — 2 contributors active in recent commits
  • Concentrated ownership — top contributor handles 73% of recent commits
  • No license — legally unclear to depend on
  • No CI workflows detected
  • 2 active contributors
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: publish a permissive license (MIT, Apache-2.0, etc.)
  • Fork & modify ConcernsMixed if: add a LICENSE file
  • Deploy as-is ConcernsMixed if: add a LICENSE file

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Signal-by-signal breakdown

kestraflink-recommandsystem-demo
Stars26,7944,473
Last commit1mo ago2y ago
LicenseApache-2.0
Open issues51618
Has tests
Has CI
Test coverage24%21%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsConcerns signals

Want the full analysis? kestra-io/kestra · water8394/flink-recommandsystem-demo

Ask AI about kestra-io/kestra vs water8394/flink-recommandsystem-demo

Open the chat with a comparison question pre-filled.