How popular Java repos run GitHub Actions

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 →

4Java repos scanned
1no dependency cache
4no job timeout
4no concurrency guard
0fully clean
RepoRuns (30d)CI min (30d)Recoverable min/moFailure rateFindings
square/retrofitgradle9453821332%5
google/gsonmaven4991,4931574%24
square/okhttppip4404,50912624%6
google/guavagradle1,0536,817*53%7

* CI min, recoverable min and failure rate cover only the latest 500 runs of a repo with more in 30 days.

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.

How does your Java repo compare?

Scan any public repo free, in seconds. No install, no card.

Scan a repo