fleetlint Policy for a fleet of repositories
v0.11 (latest)
Getting started

release/signing/android-app

Release artifacts are signed

Implements release/signing for the android-app artifact: it runs when the release publishes one (see artifacts).

Severityerror
Tiers1
Artifactandroid-app
Scoperoot
Kindoutcome
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

Requirement

The APK or AAB is signed with the release key and the workflow that publishes it verifies the signature (apksigner verify for an APK, jarsigner -verify for an AAB) or applies it (apksigner, jarsigner, a sign-android-release action). Play App Signing re-signs the AAB for distribution; the upload key signature is what the workflow checks.

Why

Checksums prove integrity; only a signature proves who built it.

Capability applies when

release.exists || repo.artifacts.size() > 0

Fix

Sign with the release key (a release signingConfig fed from CI secrets) and add apksigner verify --print-certs <apk> (or jarsigner -verify <aab>) to the release workflow; that is the signature Android checks, no cosign needed.

Agent instruction: Keep the release key’s signature and add apksigner verify --print-certs (APK) or jarsigner -verify (AAB) on the built artifact to the release workflow. Do not add cosign for the app itself.

A finding that names no file points at the first workflow that publishes the artifact, or .github/workflows/release.yml when there is none.

Sources


Generated by fleetlint docs from catalog v0.8.0.