[throwawayffffas]

Open source but make it clear that the project will not receive any updates. If any of your clients want to pick it up they will be able to fork it.

> Legal complications

If your code was written by you and you are not infringing on any patents and you don't have any client data in your repos, you should be fine I guess, but I am not a lawyer.

Just make it MIT and open it to the public. Make sure there are no keys or credentials in the repos either.

[amadeoeoeo]

Thanks for the advice. One fear I have is about security. Is the code is exposed, it will be way easier to exploit potential security flaws... I will not be able to just do nothing if this is the case .. Ill end up wanting it.

[throwawayffffas]

> It will be way easier to exploit potential security flaws.

It will be also easier for other people to find them and report or fix them.

In general it's a bad plan to rely on code secrecy for security. It's security through obscurity which never works out. All the cryptography schemes and algorithms are public. Most of the public internet runs on open source code. Transparency is a strength, not a weakness.

[ezekg]

What's to exploit? The company won't exist anymore...

[amadeoeoeo]

People's servers hosting it. I will not be officially responsible but anyway not nice. I may be just paranoid

[justinrubek]

This is the risk we accept when we use something like this. I think it's fine to put it up. If there are security issues, the community of people that use it can respond accordingly.