deepseek-ai/deepseek-v3 vs sjmoran/deeplpf-image-enhancement
deepseek-ai/deepseek-v3 shows stronger signals overall
As of June 2026, deepseek-v3 shows healthier maintenance signals than deeplpf-image-enhancement. deepseek-v3 rates Healthy overall while deeplpf-image-enhancement rates Concerns. deepseek-v3 last saw a commit 10 months ago with 26+ active contributors, 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.
deepseek-ai/deepseek-v3 →
Healthy across all four use cases
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Slowing — last commit 8mo ago
- ⚠No test directory detected
- ✓Last commit 8mo ago
- ✓26+ active contributors
- ✓Distributed ownership (top contributor 21% of recent commits)
- ✓MIT licensed
- ✓CI configured
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
sjmoran/deeplpf-image-enhancement →
Stale and unlicensed — last commit 2y ago
no license — legally unclear; last commit was 2y ago…
no license — can't legally use code; no tests detected…
Documented and popular — useful reference codebase to read through.
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 Concerns → Mixed if: publish a permissive license (MIT, Apache-2.0, etc.)
- →Fork & modify Concerns → Mixed if: add a LICENSE file
- →Deploy as-is Concerns → Mixed if: add a LICENSE file
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
Signal-by-signal breakdown
| deepseek-v3 | deeplpf-image-enhancement | |
|---|---|---|
| Stars | 103,430 | 257 |
| Last commit | 10mo ago | 1y ago |
| License | MIT | — |
| Open issues | 177 | 1 |
| Has tests | — | — |
| Has CI | ✓ | — |
| Test coverage | 0% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Concerns signals |
Want the full analysis? deepseek-ai/deepseek-v3 · sjmoran/deeplpf-image-enhancement
Ask AI about deepseek-ai/deepseek-v3 vs sjmoran/deeplpf-image-enhancement
Open the chat with a comparison question pre-filled.