You are being naive, they learned their mistake from overly putting it in plaintext source code on github.
The easiest way to achieve this, would be to post different code to github than you actually compiled in the release binary, then make the error look like a bug, such as a blue screen.
This project glued together og tinfoil, plutonium, and some other bits, none of which has this bug. And 100% of the drawing code is plutonium, which def does not have this bug which is why I believe this is intentional sabotage.
Another way to achieve this, would be to intentionally look for differences between SXOS and Atmosphere, and then write code designed to crash under SXOS. An easy example of this would be a sysmodule, such as Tesla that either through malice or incompetence, reserves way more memory than it needs to, memory it knows is not available under SXOS and thus will not run under SXOS.
I would fix it, but I have better things to do with my time unfortunately.