ci: disable `ClusterFuzzLite PR fuzzing` in private forks
What changed, and why it matters
This commit changes a GitHub Actions workflow so that an automated fuzz-testing job only runs on public copies of the repository. It does not change the Trezor firmware code, device behavior, or any security-sensitive logic. The change is purely a CI configuration fix to avoid test failures in private forks that lack authentication for the fuzzing service.
No security action required. This is a CI-only change and can be treated as routine maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit adds a conditional guard if: github.event.repository.private == false to the ClusterFuzzLite PR fuzzing job in .github/workflows/cflite.yml. This prevents the job from executing in private forks, where it would fail due to missing authentication. The change is a workflow-only quality-of-life fix with no product-code modifications.
Changed components
.github/workflows/cflite.ymlInspect captured patch +2 / −0
diff --git a/.github/workflows/cflite.yml b/.github/workflows/cflite.yml
index f53decea..39c9ea08 100644
--- a/.github/workflows/cflite.yml
+++ b/.github/workflows/cflite.yml
@@ -15,6 +15,8 @@ permissions: read-all
jobs:
PR:
+ # run only in public repositories - fuzzer will fail in private forks (missing auth)
+ if: github.event.repository.private == false
runs-on: ubuntu-latest
strategy:
fail-fast: false
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.