If you wanted to look at my entry but the *.exe makes you hesitate (no judgement there, I'm a big fan of using limited-term disposable OS's for this kind of thing) the Linux version is in the *.love file structure, for use with the Love2D system. If you have Love2D, which is opensource (ie perpetually reviewed) and free on their website, you can drag-and-drop the .love file onto Love2D's official executable in Windows and run my game's "Linux" version through the official Love2D program.
That could potentially make a difference if I were a jerk who slipped something dangerous into the code (spoilers : I'm not) because (assuming I've read the wikicorrectly) Love2D only allows the program to access files within a game-specific sub-directory that Love2D automatically creates, so there's no way to write a program that fiddles with the OS's files or sets up automated processes. It also can't access the command prompt or task scheduler or any of that nonsense - closest opportunity for mischief I can see, scanning over the Love2D wiki, is maybe calling a url into the user's preferred browser and then setting up some kind of scummy website for it to target, but given that the code would literally open a browser window over the game window that would be super obvious.
Anyway, that'd be a way to test my system through a "filter" that would keep malicious code at bay. There isn't any, but I'm just a rando on the internet, so I understand that prudence is still called for.
I've also included a copy of the code in a downloadable sourcecode zip (looking in the image directory includes spoilers!) if you wanted to do a deep dive into my program specifically.