I'll blame you for using poor quality nails, fasteners and lumber.
> If you make something publicly available for use, you should be liable for maintaining it and any damages that software causes due to bugs.
Also lets be very clear here - software bugs aren't really capable of causing damage by themselves. If I set up a lone machine running a decades old Swiss cheese Linux distribution on a publicly accessible IP, the absolute worst that can happen is its bandwidth being used to create denials of service. It's those who create real-world reliance on inadequate software systems that deserve most of the blame for damages.
No modification whatsoever is intended to have to happen to integrate that particular package with the rest of a person's house. This is completely different to how most software works, whereby dynamically linked libraries actual implementations of particular symbols can be changed out from under the user at any time. Therefore, legally speaking the demarcation of liability is far simpler to demonstrate/self-evident.
>Or electric one that have live connected to case...
Governed by electrical code.
>Surely the user is responsible not the manufacturer?
Technically yes, the user is ultimately responsible for final detection of, and escalation of the defect. If you don't engage the legal process around a defective, non compliant appliance, nothing happens/changes to fix it. The rest is implementation detail.
Don't blame me for not building the house to code, blame the guy who made my nails, fasteners, and lumber.
^this is what you're endorsing, because any failures generally occur at the stage wherein the End User is adapting the component to integrate into their own systems.
Responsibility falls on the composer of a system to deal with the composition's quirks. Anything that tries to put it up a layer is just trying to pass the buck. The Software Author has a particular case in mind. Yours is probably not it, but might become so. If it fits, go ahead and ship, if not, smooth it out. Nothing is stopping you but your unwillingness to wrangle the code.