feat(golang): detect native Go FIPS 140 mode in binaries - #5155
Merged
Conversation
Signed-off-by: Gunny Patel <zip159@gmail.com>
wagoodman
approved these changes
Aug 7, 2026
wagoodman
enabled auto-merge (squash)
August 7, 2026 14:17
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.
Description
Go 1.24 introduced a native FIPS 140-3 mode, selected at build time via the
GOFIPS140build flag and at run time via thefips140GODEBUG setting. Both are recorded in the binary's build info (GOFIPS140and thefips140=entry withinDefaultGODEBUG).Syft's existing Go crypto detection only recognized the older BoringCrypto /
crypto/tls/fipsonlymarkers, so binaries built with the new native FIPS mode were reported with no FIPS-related crypto settings at all.This adds a
getNativeFIPSSettingshelper that reads those two build settings and appends them to the existinggoCryptoSettingsmetadata field, e.g.:No new metadata field or JSON schema version is needed — the values populate the existing
goCryptoSettingslist.Type of change
Checklist