Go has dev.boringcrypto branch that holds the patches to make Go use BoringCrypto.
So, the question is: does src/crypto/internal/boring/goboringcrypto_linux_amd64.syso correspond to the FIPS certified BoringCrypto library specified here: Google's BoringCrypto FIPS 140-2 Non-Proprietary Security Policy?