Comment by hnyc

Putting the code up on, say, GitHub would also help with stopping people from doing malicious things to the site, because people aren't always mean and villainous, they can be nice as well and help out. One of the benefits is people fixing your code for you!

If you're worried that somebody will do something malicious... what is there that one could maliciously do? As long as you don't have, for example, credit cards on there, not much to steal then. Perhaps somebody is malicious enough to decide to take down your website for their perverse pleasure, in that case anybody can have their own, local copy of the library in case the internet-facing one goes down.

EDIT: What I meant and managed to completely fail to convey well in the first paragraph is that by obscuring the code, the vulnerabilities that you're afraid of people finding don't go away. And people can find them nonetheless. By opening the code, other people can fix vulnerabilities, etc. But keeping this paragraph in mind, to relate it to the others, seeing as how your library still exists, nobody seems to have bothered to try to destroy the library in the first place using their own means, so what difference will putting the source up make? :)

tl;dr: Security by obscurity? For shame. Put the source on GitHub! There's nothing to lose, and everything to gain. :)