google/exoplayer vs jboss-javassist/javassist
Both showing Mixed signals — pick on fit, not health
As of June 2026, exoplayer and javassist both show mixed maintenance signals. exoplayer last saw a commit 6 months ago with 14+ active contributors, while javassist was committed to 6 days ago with 17+ active contributors. exoplayer is Apache-2.0-licensed while javassist is Other-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
jboss-javassist/javassist →
Mixed signals — read the receipts
non-standard license (Other)
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; Scorecard "Token-Permissions" is 0/10
- ⚠Concentrated ownership — top contributor handles 69% of recent commits
- ⚠Non-standard license (Other) — review terms
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 5d ago
- ✓17 active contributors
- ✓Other licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
- →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
Signal-by-signal breakdown
| exoplayer | javassist | |
|---|---|---|
| Stars | 21,921 | 4,232 |
| Last commit | 6mo ago | 6d ago |
| License | Apache-2.0 | Other |
| Open issues | 631 | 254 |
| Has tests | — | ✓ |
| Has CI | — | ✓ |
| Test coverage | 0% | 100% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | C |
| Cycles | — | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? google/exoplayer · jboss-javassist/javassist
Ask AI about google/exoplayer vs jboss-javassist/javassist
Open the chat with a comparison question pre-filled.