fleetlint Policy for a fleet of repositories
v0.5
Getting started

release/signing/kotlin

Release artifacts are signed

Implements release/signing for kotlin.

Severityerror
Tiers1
Stackskotlin
Scoperoot
Kindoutcome
Sourcelibrary v0.2.0
Selected byfleetlint-recommended@v0.2.0

Requirement

An Android app’s APK or AAB is signed with the release key and the release workflow verifies it (apksigner verify for an APK, jarsigner -verify for an AAB) or signs it (apksigner, jarsigner, a sign-android-release action). A library published to Maven Central is signed with PGP (Gradle’s signing plugin or signAllPublications() with a publishing release, Maven’s gpg or sign plugin). Or a stack-neutral signature: cosign, GoReleaser, gpg.

Why

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

Capability applies when

release.exists && tagged_workflows().size() > 0

Fix

Android app: 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. Library: apply Gradle’s signing plugin to the Maven publication.

Agent instruction: Android app: 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. Library: apply the signing plugin to the Maven publication with the key from CI secrets. Do not add cosign for these.

See: https://fleetlint.org/baseline/#releases, https://fleetlint.org/stacks/#kotlin-jvm--android, https://developer.android.com/studio/publish/app-signing


Generated by fleetlint docs from catalog v0.2.0.