[Karunamon]

People reading your comment as entitlement really need to pay more attention to the last paragraph. People really need to stop bandying about "entitlement" as if it deflects any and all criticism.

You are, of course, free to write whatever unsafe, insecure code you want. You are, by leaving the issue tracker in Github enabled, inviting public feedback on the quality of the code you write.

When you implicitly rescind that invitation by closing issues demonstrating concrete safety problems, people are well within their rights to call out the safety issues in the project as well as your violation of reasonable expectations and community norms. And don't bother posting the "warranty disclaimer" from FOSS licenses, that's not what anyone was ever talking about.

Deleting the entire project as he did is an incredibly petty and immature response. If he just wanted to quit, the project could have been archived (made read-only) and marked unmaintained.

[catalogia]

I generally agree, except for this part: "Deleting the entire project as he did is an incredibly petty and immature response."

If he no longer wants to participate in the community, then deleting the repo was a good decision. It's not like the code is actually gone, other people have copies of it, and now that the original repo is gone nobody will mistakenly go to his repo and find it abandoned. It's basically the equivalent of boarding up the windows before you abandon a building.

[Karunamon]

Archiving the repo (which disables new commits, new issues, etc) would have served the same goal and not wasted the time of the larger community.

Here's an example from one of my own archived projects. Is there any doubt in your mind as to the state of this repository?

https://github.com/karunamon/concourse-resource-bitbucket

Inconveniencing countless others in a fit of pique is a pretty good definition of immature, petty behavior.