AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 64 Monero

Verify builder image provenance before release signing and pin latest to main

Public commit record

What the developer wrote

Authored by Keeqler

60/100 · Adequate
Verify builder image provenance before release signing and pin latest to main
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
The short version

What changed, and why it matters

This commit hardens the project's release pipeline. It makes sure the 'latest' builder Docker image tag is only updated from the main branch, and it adds a verification step before release builds that proves the builder image was actually published by the official image-building workflow on the main branch. It also checks that the Flutter version inside the builder matches the version declared in the project. These changes reduce the risk that a malicious or mismatched builder image could be used to sign or build release artifacts.

Recommended action

No immediate user action required. Reviewers should verify that the cert-identity-regex correctly anchors the expected workflow identity and that the GH_TOKEN has sufficient permissions to fetch attestations. Consider extending the same provenance verification to any other jobs or images that consume the builder image.

Security signals we found

01

Supply-chain hardening: builder image provenance verified via GitHub attestations before secrets are used

02

Tag-pinning: 'latest' Docker tag only updated from main branch

03

Mutable-tag mitigation: release builds now run from a verified digest instead of :latest

04

Version consistency check: builder Flutter version asserted against pubspec

05

Pre-secret verification: attestation check runs before Android keystore is decoded

Risk score

Why this scored 64/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 10/15
Affected reach 12/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.