I agree that publishing the source would be positive for the consumer, but I can think of lots of (variably sensible/moral/legal) reasons why they wouldn't: -

I agree that publishing the source would be positive for the consumer, but I can think of lots of (variably sensible/moral/legal) reasons why they wouldn't: - A public-facing codebase is a reflection of the company, and thus needs to be polished and maintained in a way that a private one doesn't. - You might have trade secrets in your code base that you don't want your competitors to have - Even without explicit secrets, your code base is a substantial investment that any competitor will need to make themselves in order to enter the market; publishing the code would give that to everyone (and let's not pretend that licensing terms and copyright will prevent a knock-off hardware manufacturer in a less cooperative country from reusing the code wholesale) - Alongside the free security fixes, you give adversaries more opportunity to look for, and exploit, flaws in your security. - The IP represented by the source code has a value that might well be a substantial part of your company's valuation, in which case you might need to sell it as part of an acquisition/bankruptcy proceeding. - (I am not accusing Insteon of this, but) if you publish your source code, you may expose all the 3rd-party code you are using/modifying whose license terms you may not be respecting.