For cryptography it uses the ring-library which still relies on C-Code in many places. Additionally there is no API-stability (still v0.*) and the last official audit was 3 years ago.
The project has potential but isn't quite ready for prime time yet.
Why put the commit message there then? You could just use a git-client that adds this text as description for commits. There is generally little use to store automatically generated content in databases, the input for generation should be enough.
Attack complexity High (chance for an attacker to get anything at all is very low), Availability None (you're not crashing any service that's running in the background) and Confidentiality Low (data leaked is not in the attackers control and not likely to be interesting).
Adds up to a score of 2.9
Mentioning Greenland ice sheet in this context is always a bit of a red herring.
It is important to note that in the language of these simulations no "overshoot" is included in the temperature trajectory. A 1.5°C global warming is talking about the long term (millenial timescale) stable temperature we reach after our little "experiment".
If we can "quickly" (a few hundred years) return to 1.0°C or even less warming, compared to pre-industrial levels, these tipping points have not actually happened yet. (https://www.researchsquare.com/article/rs-1418830/latest.pdf summarizes this very well)
Nico Wunderling shows that while for some systems (like the Amazon rain forrest) peak temperature (even over only a few years) is most important, for slower systems like the Greenland ice sheet the target, long-term temperature is most dominant.
Priotizing the most urgent matter should therefor lead us to talk about the quickly acting tipping points, often related to biological ecosystems. For those it is most important to actually stay below 2°C of warming. For the Greenland ice shield there is ample time after the year 2100 for us to prevent the worst.
"when there's clouds and the wind doesn't blow, what happens?" Meteorologically speaking that won't happen over a large enough area like Europe or USA. When there's clouds there's always wind close by. It's also never cloudy over a whole continent (air has to come back down somewhere)
That is just to show that nuclear isn't a magical always-on power source that some of the pro-nuclear folks make it out to be. Also: we can install twice the capacity in MW for solar and still have money left over to put into a smarter grid or storage compared to nuclear.
A good estimate to gauge the societal investment needed to generate electricity in a certain way, is to look at its total cost in dollar/MWh. Wikipedia has a nice graphic prepared for just that: https://en.wikipedia.org/wiki/Cost_of_electricity_by_source#... (which ignores externalized costs like CO2 or nuclear waste)
You can see in there that nuclear has triple the cost compared to solar.
As we need to replace as much fossil-fueled power plants as possible and as quickly as possible, wasting ressources into building nuclear power plants sounds stupid.
Other interesting factors:
Sentences that apparently mark cognitive distortion:
"The quality of our product is not acceptable yet.",
"I won't go to this meeting, because I feel nauseous.",
"Children should go to school."
I think this is trying to solve delivery inside cities. However, I don't see cities beeing clogged by parcel delivery services. Transportation of goods is more problematic on the inter-city level. But that's too far to build a tunnel.
What is causing troubles for cities seems to mostly be human traffic (that's why rush-hour is a thing) - for that subways could indeed be a solution.
Unless Switzerland's traffic is looking completly different from what I know from Germany of course?
What fans of unsigned integers seem to really want is array access in the form of x[i %mod% LEN]. While signed integers "kind of" give you an error on overflow (Except your unlucky or somebody was malicious).
Is there a way to combine both? As in give me an error on overflow for "debug builds" and always mod-LEN on "release builds"?
The project has potential but isn't quite ready for prime time yet.