How is a one person fork of Go in any way going to ever be more secure than the original which is developed by many people? Why should I trust your changes? Is this actually an adversarial project that will hide and rug pull down the road?
2. "How is a one person fork of Go in any way going to ever be more secure than the original which is developed by many people? " - Read the README.
3. "Why should I trust your changes?" - You don't have to. The same reasons you don't have to trust the Github project you're cloning.
4. "Is this actually an adversarial project that will hide and rug pull down the road?" - Read the code.
Sarcasm aside, the objective is "helping to find bugs in Go codebases via built-in security implementations". That's mainly used for fuzzing and testing. Don't deploy you compiled binary on production with that compiler.
SQLite's temp file prefix was originally "sqlite_" until McAfee's antivirus started creating temp files in Windows' `c:/temp` folder, frustrating users who then tracked down and called SQLite developers to complain. In response, the prefix was changed to "etilqs_" (SQLite reversed).
