You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Inclusion of example JWT in README.md is being flagged by secret scanning #36
My employer has a Go repository which uses echo-jwt as a dependency, referenced as part of the vendored files in go.mod. The example JWT included in the README.md (both in a sample call and response) is getting flagged as an issue by secret scanning software. We can add an exclusion for this specific JWT as a work-around, but perhaps a documentation update to a use a placeholder would also be appropriate?
Thanks for the quick reply! The ticket being opened on our side begins:
Finding Name:
HTTP bearer authentication header
Finding Description:
GitHub Advanced security has discovered a secret in the repository "[repository name]" using the secret scanning pattern "HTTP bearer authentication header"
and simply highlights the full JWT text content. I believe more details are here.
I think changing the content of the token to something like YOURTOKEN would resolve the issue.
Activity
aldas commentedon Oct 13, 2025
I assume
[]byte("secret")is the problematic part? IF you propose something that will pass your checks we probably can change it so.castellotti commentedon Oct 13, 2025
Thanks for the quick reply! The ticket being opened on our side begins:
and simply highlights the full JWT text content. I believe more details are here.
I think changing the content of the token to something like
YOURTOKENwould resolve the issue.aldas commentedon Oct 13, 2025
Ok, if it is Github then ChatGPT suggets that
https://docs.github.com/en/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/excluding-folders-and-files-from-secret-scanning
aldas commentedon Oct 13, 2025
PR for
github/secret_scanning.ymlwould be OK from our sidecastellotti commentedon Oct 13, 2025
Thanks again, I have created a PR with the suggested change.
aldas commentedon Oct 14, 2025
alright, PR is merged, I hope it helps.