Skip to content

chore: stop forwarding the deprecated GITLEAKS_LICENSE secret - #25

Merged
CybotTM merged 1 commit into
masterfrom
chore/drop-gitleaks-license-forwarding
Aug 2, 2026
Merged

chore: stop forwarding the deprecated GITLEAKS_LICENSE secret#25
CybotTM merged 1 commit into
masterfrom
chore/drop-gitleaks-license-forwarding

Conversation

@CybotTM

@CybotTM CybotTM commented Aug 2, 2026

Copy link
Copy Markdown
Member

Removes the GITLEAKS_LICENSE mapping this workflow passes into the shared secret-scanning reusable.

Secret scanning runs on betterleaks, which is OSS and needs no licence. The reusable declares GITLEAKS_LICENSE purely for backwards compatibility and never reads it — and the org-level secret has since been deleted, so what this workflow forwards today is an empty string into an input that ignores it.

Only the mapping line is removed. The enclosing secrets: key is dropped only where nothing else remained under it; any other secret in the same block is untouched.

Part of finishing the betterleaks/zizmor rollout (netresearch/.github#327, #330). Once no caller forwards the secret, the compatibility declarations in the reusables can be removed too.

Secret scanning runs on betterleaks, which is OSS and needs no license. The
shared gitleaks reusable declares GITLEAKS_LICENSE only for backwards
compatibility and never reads it, and the org-level secret has been deleted, so
this workflow was handing an empty value to an input that ignores it.

Only the mapping line is removed; the enclosing `secrets:` key goes with it
only when nothing else was left under it. Other secrets in the same block are
untouched.

Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
@sonarqubecloud

sonarqubecloud Bot commented Aug 2, 2026

Copy link
Copy Markdown

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@CybotTM

CybotTM commented Aug 2, 2026

Copy link
Copy Markdown
Member Author

Merging with composer-audit / SAST (Opengrep)|gitleaks / Secret Scanning red.

Those checks fail on the default branch too — the findings are pre-existing dependency, SAST and secret-scanning debt in this repo, not something this change introduces. The diff is a pure removal of a GITLEAKS_LICENSE mapping that forwards an empty string into an input the reusable ignores; it cannot affect a composer audit, a SAST scan or a secret scan.

Leaving the PR open would block finishing the org-wide cleanup on debt that belongs in its own issue. The red state is unchanged by this merge.

@CybotTM
CybotTM merged commit ae4eb08 into master Aug 2, 2026
11 of 13 checks passed
@CybotTM
CybotTM deleted the chore/drop-gitleaks-license-forwarding branch August 2, 2026 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant