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).
| Severity | error |
| Tiers | 1 |
| Artifact | android-app |
| Scope | root |
| Kind | outcome |
| Source | library v0.5.0 |
| Selected by | fleetlint-recommended@v0.5.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() > 0Fix
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 of this rule points at the file artifact.workflows.size() > 0 ? artifact.workflows[0] : ".github/workflows/release.yml" yields.
Sources
- https://csrc.nist.gov/pubs/sp/800/218/final (standard, PS.2.1: Make software integrity verification information available to software acquirers)
- https://github.com/ossf/scorecard/blob/main/docs/checks.md (standard, Signed-Releases)
- https://fleetlint.org/baseline/#releases
- https://developer.android.com/studio/publish/app-signing (spec)
Generated by fleetlint docs from catalog v0.5.0.