RepoPilot

programthink/zhao vs sjmoran/deeplpf-image-enhancement

Both showing Concerns signals — pick on fit, not health

As of June 2026, zhao and deeplpf-image-enhancement both show concerning maintenance signals. zhao last saw a commit 4 years ago with 1+ active contributor, while deeplpf-image-enhancement last saw a commit 1 year ago with 4+ 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.

programthink/zhao

Concerns

Looks unmaintained — solo project with stale commits

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility; last commit was 5y ago…

MixedFork & modify

no tests detected; no CI workflows detected…

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

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

  • Stale — last commit 5y ago
  • Solo or near-solo (1 contributor active in recent commits)
  • GPL-3.0 is copyleft — check downstream compatibility
  • No CI workflows detected
  • No test directory detected
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (0/10)
  • GPL-3.0 licensed

What would improve this?

  • Use as dependency ConcernsMixed if: relicense under MIT/Apache-2.0 (rare for established libs); 1 commit in the last 365 days
  • Fork & modify MixedHealthy if: add a test suite
  • Deploy as-is MixedHealthy if: 1 commit in the last 180 days; bring "Branch-Protection" to ≥3/10 (see scorecard report)

Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests + OpenSSF Scorecard

sjmoran/deeplpf-image-enhancement

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 tests 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 — 4 contributors active in recent commits
  • Concentrated ownership — top contributor handles 64% of recent commits
  • No license — legally unclear to depend on
  • No CI workflows detected
  • No test directory detected
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (0/10)
  • 4 active contributors

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

Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests + OpenSSF Scorecard

Signal-by-signal breakdown

zhaodeeplpf-image-enhancement
Stars13,984257
Last commit4y ago1y ago
LicenseGPL-3.0
Open issues3841
Has tests
Has CI
Test coverage0%0%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineConcerns signalsConcerns signals

Want the full analysis? programthink/zhao · sjmoran/deeplpf-image-enhancement

Ask AI about programthink/zhao vs sjmoran/deeplpf-image-enhancement

Open the chat with a comparison question pre-filled.