Interesting. It seems Ruby's YAML module has undergone a log4j-style progression where it gains more and more parsing modes, which leads to an ever-expanding vu

Interesting. It seems Ruby's YAML module has undergone a log4j-style progression where it gains more and more parsing modes, which leads to an ever-expanding vulnerability surface area. This is a last-ditch attempt to protect users from that by making the "safe" parser the default. But I wonder how long until the "safe" parser also supports many things other than strictly parsing YAML, and then we'll need a "super-safe" mode to set the default to.