While I agree in general that PRs are better than forks, I don't think what you're saying is totally fair. Your choice of licensing explicitely allows forks (and almost anything else) to happen. There have been many discussions on the topic [1], and there is no easy solution.

Then, your choice of words is not ideal:

>NOTE: I no longer actively maintain this package. I'd love to get PRs to keep it going though!

If it's not maintained anymore then I as a developer don't really gain anything (bugfixes, features) by submitting a PR vs. just forking myself. So the choice to fork is understandable, even if it's not what you intended to happen.

[1] https://arstechnica.com/information-technology/2014/10/how-d...