JVM builds resolve a lot of dependencies, and setup-java caches Gradle or Maven with its one-line cache: option. Each card below shows which build tool the project uses. Here is how the JVM projects everyone depends on actually run CI. Read the fix →
| Repo | Runs (30d) | CI min (30d) | Recoverable min/mo | Failure rate | Findings |
|---|---|---|---|---|---|
| google/gsonmaven | 500+ | 5,323 | 454 | 8% | 22 |
| square/retrofitgradle | 43 | 346 | 121 | 26% | 6 |
| square/okhttppip | 500+ | 3,782 | 40 | 30% | 9 |
| google/guavagradle | 500+ | 4,038 | 4 | 1% | 7 |
Public data from each repo's GitHub Actions. Minutes are wall-clock workflow time over 30 days. These repos run Actions free (public repos always do). Each scorecard shows the private-repo dollar equivalent as a labeled estimate. Repo owners can remove their scorecard any time.
Scan any public repo free, in seconds. No install, no card.
Scan a repo