JUnit Report Action vs xray-action
Side-by-side comparison of mikepenz/action-junit-report and mikepenz/xray-action: composite score, security signals, maintenance and popularity — refreshed daily.
| Metric | JUnit Report Actionmikepenz/action-junit-report | xray-actionmikepenz/xray-action |
|---|---|---|
| ActionRank score | B81 / 100 | B78 / 100 |
| Maintenance (30%) | 100 / 100 | 100 / 100 |
| Popularity (20%) | 54 / 100 | 36 / 100 |
| Security (35%) | 75 / 100 | 76 / 100 |
| Reliability (15%) | 96 / 100 | 92 / 100 |
| Maintenance status | Actively maintained | Actively maintained |
| Stars | ★ 429 | ★ 61 |
| Last commit | today | 12 days ago |
| Latest version | v6.6.2 | v4.2.0 |
| License | Apache-2.0 | Apache-2.0 |
| OpenSSF Scorecard | 7.5 / 10 | 7.7 / 10 |
| Known advisories | None on record | None on record |
| SECURITY.md | Yes | Yes |
| Immutable releases | Not enabled | Not enabled |
| Archived | No | No |
Verdict
JUnit Report Action comes out ahead: 81/100 (grade B) versus 78/100 (grade B) for xray-action — a 3-point gap on the ActionRank scale.
Metrics from the GitHub API, security score from OpenSSF Scorecard, advisories from OSV.dev. JUnit Report Action last updated Oct 31, 2026; xray-action last updated Oct 26, 2026. See our methodology.