RepoPilot

nautechsystems/nautilus_trader vs postgresml/pgcat

Both showing Mixed signals — pick on fit, not health

As of September 2026, nautilus_trader and pgcat both show mixed maintenance signals. nautilus_trader was committed to 1 week ago with 5+ active contributors, while pgcat last saw a commit 1 year ago with 37+ active contributors. nautilus_trader is LGPL-3.0-licensed while pgcat is MIT-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.

nautechsystems/nautilus_trader

Mixed

Single-maintainer risk — review before adopting

ConcernsDependency

copyleft license (LGPL-3.0) — review compatibility; top contributor handles 94% of recent commits

HealthyFork & modify

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

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • Single-maintainer risk — top contributor 94% of recent commits
  • LGPL-3.0 is copyleft — check downstream compatibility
  • Last commit today
  • 5 active contributors
  • LGPL-3.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)

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

postgresml/pgcat

Mixed

Stale — last commit 1y ago

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

last commit was 1y ago; Scorecard "Branch-Protection" is 0/10…

  • Stale — last commit 1y ago
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (0/10)
  • 37+ active contributors
  • Distributed ownership (top contributor 22% of recent commits)
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days; 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

nautilus_traderpgcat
Stars28,3304,009
Last commit13d ago1y ago
LicenseLGPL-3.0MIT
Open issues129201
Has tests
Has CI
Test coverage14%100%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeAC
Cycles08
Bottom-lineMixed signalsMixed signals

Want the full analysis? nautechsystems/nautilus_trader · postgresml/pgcat

Ask AI about nautechsystems/nautilus_trader vs postgresml/pgcat

Open the chat with a comparison question pre-filled.