Skip to content

chore: Add a .gitleaks.toml to fix the false/positives from the infosec scans #2452

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lholmquist wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −0
Open

chore: Add a .gitleaks.toml to fix the false/positives from the infosec scans #2452

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .gitleaks.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
[allowlist]
description = "Global Allowlist"

regexes = [
'''ABTLWHOULUVAXGTRYU7OC2876QJ2O''',
'''GR1348941oP5naQnWsbJRTvXHC7VJ''',
'''ghs_16C7e42F292c6912E7710c838347Ae178B4a''',
]
Comment on lines +1 to +8
Copy link

@rhdh-qodo-merge rhdh-qodo-merge bot Mar 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Global token allowlist 🐞 Bug ⛨ Security

The new .gitleaks.toml globally allowlists full token-like values, meaning if any of these values
ever appear outside the intended test fixtures, gitleaks will silently ignore them and you may miss
a real leak. Since these values come from test fixtures, a safer approach is to redact/replace them
in fixtures (or scope allowlisting to fixture paths) rather than allowlisting the raw token strings
repo-wide.
Agent Prompt 
## Issue description
A repo-wide gitleaks allowlist containing full token-like values suppresses detection everywhere and keeps realistic token strings in the repository.

## Issue Context
The allowlisted strings appear to come from bulk-import backend MSW fixtures.

## Fix Focus Areas
- .gitleaks.toml[1-8]
- workspaces/bulk-import/plugins/bulk-import-backend/__fixtures__/github/app/installations/app-installation-1-access-tokens.json[1-4]
- workspaces/bulk-import/plugins/bulk-import-backend/__fixtures__/github/repos/my-ent-org-2/A2/repo.json[205-223]
- workspaces/bulk-import/plugins/bulk-import-backend/__fixtures__/github/user/repos.json[94-103]
- workspaces/bulk-import/plugins/bulk-import-backend/__fixtures__/handlers.ts[24-36]
- workspaces/bulk-import/plugins/bulk-import-backend/__fixtures__/handlers.ts[53-64]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools