They actually do use "os/user".Lookup() as a fallback if fetching via getent(1) fails, so they might be using NSS modules to dynamically define users and then not linking their binaries with glibc (musl and the opt-in pure-Go implementation of "os/user".Lookup() do not support NSS).
Still, requesting the information from systemd-userdb would be a better way of doing this if it's really necessary.
Still, requesting the information from systemd-userdb would be a better way of doing this if it's really necessary.
EDIT: Yeah, some older comments confirm that was their reasoning. https://github.com/tailscale/tailscale/commit/1fc1077052dfa7...