cassete beasts is a pokemon-like game, that wont require to much power.
ember knights is very simmiliar to hades, both are great roguelikes.
doom2, blood, duke nukem 3d etc run with low power consumption.
a hat in time is a 3d jump n run that can ve limitted to 10 watt tdp (maybe less)
pillars of eternity, great game so far, did not play a realtime-with-pause rpg since kotor, but thanks to the auto-pause settings this plays really well. And while i can’t claim to understand whats going on right now, the world seems to be really fleshed out and combats so far where very fun.
brotato, fun take on the vampires survivor formular.
backpack battles, an autobattler, but players don’t draft from a shared pool, so you’ll mostly draft the same builds everytime and don’t care much about the builds you are dacing. not somerhing i’ll continue playing, but it was ok to waste a bit of time, would probably be cool on mobile.
doom2, but i am allways playing doom, so i guess that does not count.
It was written as part of my work.
check your contract, you might not own the code and your organization may have a process to determine how to license something.
to your other questions (IANAL)
no, the solution is not to pay someone to have someone to blame if shit happens.
there are a bus load of people involved on the way from a git repo to actuall stuff running on a machine and everyone in that chain is responsible to have an eye on what stuff they are building/packaging/installing/running and if something seems off, it’s their responsibility to investigate and communicate with each other.
attacks like this will not be solved by paying someone to read source code, because the code in the repo might not be what is going to run on a machine or might look absolutely fine in a vacuum or will be altered by some other part in the chain. and even if you have dedicated code readers, you cant be sure that they are not compromised or that their findings will reach the people running/packaging/depending on the software.
i can’t see how paying someone would have changed anything in this scenario.
this seems to be a long running campaign to get someone into a position where they could introduce malicious code. the only thing different would have been that the bad actor would have been paid by someone.
this is not to say, that people working on foss should not be paid. if anything we need more people actively reviewing code and release artifacts even if they are not a contributor or maintainer of a piece of software.
Had issues like that from time to time, when graphics drivers got borked during the update/did not exist for the new kernel.
solution was allways to either remove the drivers and reinstall them or rollback to an earlier snapshot and wait a week.