The Go macOS installer currently runs a sequence of commands described as "Fixing permissions":
GOROOT=/usr/local/go
echo "Fixing permissions"
cd $GOROOT
find . -exec chmod ugo+r \{\} \;
find bin -exec chmod ugo+rx \{\} \;
find . -type d -exec chmod ugo+rx \{\} \;
chmod o-w .
(Source: https://cs.opensource.google/go/x/build/+/master:internal/installer/darwinpkg/darwinpkg.go;l=83-89;drc=b373e4e0904d79d3f500fe3943a3d7bde88662c8.)
This behavior has apparently existed going as far back as go1.2.2, possibly older. The earliest mention of it being introduced I found so far is CL 11970 from 2015. (CC @adg.)
One of the lines is adding execute permission to files in the GOROOT/bin directory, and so it's unusual to see that it's not also doing something equivalent for the files in the GOROOT/pkg/tool directory where installed tool binaries are placed.
Given that this step was added before signing/notarization, relui, distpack, it's quite possible that the reason to need to "fix permissions" is obsolete by now. It's also possible that it's still needed, if there are some cases where something beyond the control of our tooling—such as the macOS installer itself—changes permissions.
This issue is to either confirm that this postinstall sequence of commands is still needed in 2025 and update the comment to clarify why, or to confirm that it has no effect and stop including it in some future major Go release. It would be highly preferable to get an understanding why it was needed in the first place, as knowing that the original reason no longer applies would increase confidence that it's safe to proceed with removing it.
CC @golang/release.