I understand what you're saying, but Forgejo has an outdated and made-up-from-thin-air policy. From their security.md:

• You MUST disclose vulns to the author (why are we dictating instead of inviting participation)
• emails about vulns MUST be encrypted (I don't even understand this one, this gives really strong "we don't know how email works" vibes)

And it just goes on, like someone from 2003 wrote that policy.

Now, I'm going to agree with you that it's a bit of a dick move to do the carrot dangle thing, but some vendors/devs just don't respond without the pressure. And forgejo has been forced by github supporters to implement a security policy after trying to ignore it.

It seems that the author has some ongoing interactions with forgejo, and it would be great if these were disclosed in the article, but forgejo seems to need a kick in the pants, especially over an RCE, the forbidden sev 10 of vulns.