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 |
|---|---|---|---|---|---|
| square/retrofitgradle | 70 | 400 | 159 | 41% | 5 |
| google/gsonmaven | 422 | 1,117 | 108 | 2% | 21 |
| square/okhttppip | 219 | 1,450 | 7 | 45% | 6 |
| google/guavagradle | 581 | 6,005* | 5 | 3% | 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.
Scan any public repo free, in seconds. No install, no card.
Scan a repo