147
Dev rejects CVE severity, makes his GitHub repo read-only
(www.bleepingcomputer.com)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
I find this outcome delightful for all the compliance mandated organizations that are leaching with no intention to contribute back.
It could be really helpful for developers at pure leech organizations to make a case for being ready to contribute in an agile manner.
Now they're all stuck waiting on either a good Samaritan, or their lawyers to get out of the way of progress.
I have little doubt that the fix has been committed to private forks dozens of times already, of course.
This whole debacle is a festival of stupidity:
ip.isPrivate()
, which you can write yourself in 5 minutes.At this point the maintainer is fucked no matter what they do, so archiving the project and telling everybody to fuck off right back was really the only sane thing to do.