Hi @SimonGurney, all semi-generic regexes follow a similar pattern to that of https://github.com/zricethezav/gitleaks/blob/master/config/gitleaks.toml#L74, for example. I generate these rules with a utility here https://github.com/zricethezav/gitleaks/blob/master/cmd/generate/config/main.go.

I can add this sometime in the next two weeks if you haven't gotten to it already

I'll get a PR in tomorrow. So does the keyword need to be found in the document for the regex to find the secret?

@SimonGurney yes, the keyword is essentially a ROI marker or prefilter. If a git patch fragment does not contain a the keyword, that rule can be ignored.

Ok understood. I think in most cases the word "Algolia" would be on the same line, but it's definitely not required and I imagine a diff which changes the key could be as simple as

Key=[key]

Would you want the keyword including or not? I guess it's a balance between eliminating false positives and missing secrets right?

but it's definitely not required and I imagine a diff which changes the key could be as simple as Key=[key]

I don't follow

Would you want the keyword including or not? I guess it's a balance between eliminating false positives and missing secrets right?

Keywords should always be included to reduce fps and help performance. The generic key would likely catch keys that don't contain Algolia

Makes sense, I'll raise the PR tomorrow.

Thanks for your help 😃

Is this what you were thinking, I just based it off old PRs, or do you want me to use the rule generator and add one to here cmd/generate/config/rules/?

@zricethezav are you happy with the PR?