Conversation
Co-authored-by: al1dazzi <247480224+al1dazzi@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Remediate token detection using secrets manager
Remove hardcoded GitHub token fixture and return non-sensitive token state
Sep 11, 2026
This branch has not been deployed
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
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.
This PR addresses a Reachable secret finding in
internal/handlers/secrets.gowhere a committed GitHub token-like literal was returned by a handler. The change removes the literal and keeps runtime behavior useful without exposing secret values.Secret sink remediation (
CloudTokens)syntheticGitHubTokenconstant from source.REACH_TESTBED_GITHUB_TOKEN:"configured"when present"not_configured"when absentaws_access_key_idremains unchanged).Regression coverage for secret non-echo behavior
internal/handlers/secrets_test.goto verify: