Skip to content

ci: scan the release APK's libraries with OSV-Scanner, and raise Guava past an advisory - #59

Draft
ricaezejo wants to merge 2 commits into
sayed0am:mainfrom
ricaezejo:ci/osv-scanner
Draft

ricaezejo wants to merge 2 commits into
sayed0am:mainfrom
ricaezejo:ci/osv-scanner

Conversation

@ricaezejo

@ricaezejo ricaezejo commented Nov 8, 2026 •

Copy link
Copy Markdown

Adds a dependency scan for the libraries the release APK ships, and fixes the one advisory it found.

Guava fix

OSV-Scanner flagged Guava 32.0.0 in the release APK (GHSA-xxph-c9ww-hj94: unbounded memory use when Guava collections are deserialized). It comes in through Health Connect's client via kotlinx-coroutines-guava. A constraint in app/build.gradle.kts raises it to the fixed 33.7.2-android. The app likely never deserializes Guava collections, but the fix is one line.

Dependency scan workflow (osv-scanner.yml)

  • Runs on push, pull request and every Monday, since new advisories arrive without any code change.
  • Gradle keeps no lockfile, so CI writes one for :app releaseRuntimeClasspath through an init script (.github/scripts/lock-all.gradle.kts). Nothing is committed, so dependency bumps never need a relock. Build tools (lint, KSP) and test libraries are left out, since they never reach a phone. A full scan finds 16 more advisories there.
  • The OSV-Scanner binary is pinned to v2.7.0 and checksum-verified.

Checked locally: without the Guava fix the scan reports the advisory and exits 1; with it, no issues and exit 0. The tests, lint and detekt still pass with the new Guava.

🤖 Generated with Claude Code

ricaezejo and others added 2 commits November 8, 2026 22:40
Health Connect pulls Guava 32.0.0 into the release APK through
kotlinx-coroutines-guava. A constraint lifts it to 33.7.2-android, the fixed release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On push, pull request and weekly, since new advisories arrive without any code
change. Gradle keeps no lockfile, so CI writes one for releaseRuntimeClasspath
through an init script; nothing is committed, so dependency bumps need no relock.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant