Having once worked on an open source project that dealt with providing anonymity - it was considered the duty of the release engineer to have an overview of all code committed (and to ask questions, publicly if needed, if they had any doubts) - before compiling and signing the code.
On some months, that was a big load of work and it seemed possible that one person might miss something. So others were encouraged to read and report about irregularities too. I don't think anyone ever skipped it, because the implications were clear: "if one of us fails, someone somewhere can get imprisoned or killed, not to speak of milder results".
However, in case of an utility not directly involved with functions that are critical for security - it might be easier to pass through the sieve.
A note about Taiwan. Allegedly, Putin asked Musk for a favour for Xi - to refuse Starlink for Taiwan.
Coincidentally, negotiations between Taiwan and Starlink broke down. The Guardian reported about it on October 15:
https://www.theguardian.com/world/2024/oct/15/taiwan-to-have-satellite-internet-service-as-protection-in-case-of-chinese-attack
A person experienced in investigating such matters would take a look at the ownership structure of other Starlink local representatives, and see if Taiwan had unusually harsh demands or Musk was unusually stiff while negotiating with them. If Taiwan had harsh demands, it is plausible that no favour was done. If Musk was unusually stiff, then it's plausible that the favour was done as requested.