But what does a developer (open source or not) who releases a container format parser and codec collection upon the world expect people to do with it if not run it on malicious data on personal devices?
Sometimes you build things to explore how they work, or to test your assumptions about how something would work. To build your own knowledge about a format, language, or system. Hell, sometimes it's just the middle of a venn diagram between fun and practice.
And, because it's easy to throw something up on GitHub, you can say "Look at this cool thing I made", "Look, I actually can do what I claim on my resume", or "Anyone struggling in the same place as me can use this as an example workaround, or inspiration for a solution"
Nobody has to, or is even necessarily expected, to use it. Sometimes it's just the author sharing this cool thing they made.
Typically it's presented as-is and without any form of warranty, but in the hope it will be useful - not "suitable for critical infrastructure".
Perhaps those using it for "critical infrastructure" can write their own utilities, or chip in to support the developer whose hard work they apparently rely so heavily on, so bug fixes aren't done merely in the dev's unpaid time-off?