google/exoplayer vs java-decompiler/jd-gui
Both showing Mixed signals — pick on fit, not health
As of June 2026, exoplayer and jd-gui both show mixed maintenance signals. exoplayer last saw a commit 6 months ago with 14+ active contributors, while jd-gui last saw a commit 1 year ago with 4+ active contributors. exoplayer is Apache-2.0-licensed while jd-gui is GPL-3.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.
google/exoplayer →
Slowing — last commit 5mo ago
no tests detected; no CI workflows detected
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; no CI workflows detected
- ⚠Slowing — last commit 5mo ago
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 5mo ago
- ✓14 active contributors
- ✓Distributed ownership (top contributor 27% of recent commits)
- ✓Apache-2.0 licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: add a test suite
- →Deploy as-is Mixed → 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 OpenSSF Scorecard
java-decompiler/jd-gui →
Stale — last commit 2y ago
copyleft license (GPL-3.0) — review compatibility; last commit was 2y ago…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; no CI workflows detected
- ⚠Stale — last commit 2y ago
- ⚠Small team — 4 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 95% of recent commits
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠No CI workflows detected
- ✓4 active contributors
- ✓GPL-3.0 licensed
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| exoplayer | jd-gui | |
|---|---|---|
| Stars | 21,921 | 15,083 |
| Last commit | 6mo ago | 1y ago |
| License | Apache-2.0 | GPL-3.0 |
| Open issues | 631 | 247 |
| Has tests | — | ✓ |
| Has CI | — | — |
| Test coverage | 0% | 5% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? google/exoplayer · java-decompiler/jd-gui
Ask AI about google/exoplayer vs java-decompiler/jd-gui
Open the chat with a comparison question pre-filled.