Seems fairly standard for Go. You mentioned requests - the Go net/http library is widely used, even though it's in the standard library. It didn't languish, it

Seems fairly standard for Go. You mentioned requests - the Go net/http library is widely used, even though it's in the standard library. It didn't languish, it didn't die. The interfaces are also used in most 3rd party libraries and work well. Moreover, Go's quality standard library is often cited as one of its main strengths. Thus, the inclusion of fuzzing in the stdlib isn't surprising to me. Not saying the other way around would be bad. It's just not surprising, and I don't think it's a bad choice, looking at Go historically.