RepoPilot

infiniflow/ragflow vs tyktechnologies/tyk

Both showing Healthy signals — pick on fit, not health

As of September 2026, ragflow and tyk both show healthy maintenance signals. ragflow last saw a commit 1 month ago with 22+ active contributors, while tyk was committed to 3 weeks ago with 26+ active contributors. ragflow is Apache-2.0-licensed while tyk is MPL-2.0-licensed. 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.

infiniflow/ragflow

Healthy

Strong maintenance signals

MixedDependency

dependency CVE scan unavailable

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; dependency CVE scan unavailable

  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 22+ active contributors
  • Distributed ownership (top contributor 19% of recent commits)
  • Apache-2.0 licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

tyktechnologies/tyk

Healthy

Strong maintenance signals

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10

  • Scorecard: dangerous CI workflow (0/10)
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 26+ active contributors
  • Distributed ownership (top contributor 20% of recent commits)
  • MPL-2.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

ragflowtyk
Stars88,63410,798
Last commit1mo ago22d ago
LicenseApache-2.0MPL-2.0
Open issues1,792497
Has tests
Has CI
Test coverage43%100%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeC
Cycles0
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? infiniflow/ragflow · tyktechnologies/tyk

Ask AI about infiniflow/ragflow vs tyktechnologies/tyk

Open the chat with a comparison question pre-filled.