SK-3016-gitleaks-detection-multiple-secret-exposures-identified - #237
Merged
Conversation
…E.md Adds .gitleaksignore with a fingerprint for the flagged generic-api-key finding at README.md:2711 — a UUID-format sample token in the Sample Response documentation block, not a real credential. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep findings: No issues found, Good to merge. |
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
1 participant
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.
Why:
The org-wide Gitleaks scan flagged a generic-api-key finding in README.md (line 2711) — a sample UUID-format token ID in the "Sample Response" documentation block that matches the secret-detection pattern. This is an illustrative example value from API response docs, not a real credential, but the finding needs to be resolved to close out the security review.
Goal:
Suppress the false-positive finding without altering the visible README content (so SDK consumers still see the real, realistic sample response), by adding a .gitleaksignore file with a fingerprint for the specific finding — Gitleaks' native, built-in suppression mechanism for exactly this case.
Ref: same pattern as skyflow-react-native#157.
Jira: SK-3016
🤖 Generated with Claude Code