Add new Looker client ID and client secret rules#1947
Merged
zricethezav merged 1 commit intogitleaks:masterfrom Nov 20, 2025
Merged
Add new Looker client ID and client secret rules#1947zricethezav merged 1 commit intogitleaks:masterfrom
zricethezav merged 1 commit intogitleaks:masterfrom
Conversation
Contributor
Author
|
Closes #1946 |
zricethezav
approved these changes
Nov 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Add two provider-specific rules to detect leaked Looker SDK API3 credentials: looker-client-id and looker-client-secret. These rules target alphanumeric client_id (20 chars) and client_secret (24 chars) commonly committed in configuration (for example, looker.ini), environment variables, and inline literals. The implementation uses SemiGeneric patterns keyed on the “looker” identifier plus deterministic length constraints. This helps prevent unauthorized access to Looker instances and sensitive analytics data.
Checklist:
Not applicable