Mostly. There are some exceptions. For example, with cars, tires are often warrantied directly with the tire manufacturer. Also, in the case of material defect, e.g. the airbag issue a number of years back, the auto manufacturer is mostly the entity on the hook for consumers but there are absolutely various liabilities up the supply chain.
For sure, it’s reasonable that the airbag vendor, having sold a product to the auto vendor, is liable to the auto vendor.
I don’t think the airbag vendor should be separately liable to the user since it’s the auto vendor’s responsibility to ensure that the holistic system works- even without considering the case of open source wherein there’s no contract at all between the OSS “vendor” and either the immediate “buyer” or end customer.
Takata was sued by various parties (consumer class actions, at least one state) over their airbag defect although I'm not sure what the outcome was over and above the settlement by the various auto makers.
People can sue for pretty much anything and there's a good chance you have to (or at least should) get a lawyer if that happens. While it's arguably negligible, there is some risk in putting tools/code out there even if it's free and not warrantied.
Not sure about tires, but atleast here, the seller has to deal with warranties, even if the warranty is made by the manufacturer... so if i buy a Sumsing(TM) phone, I don't have to drive half a country away for them to service it, but I can just drop it at the shop I bought it at and have them deal with it.
If something warranty-worthy happened with a tire, I'd just take it to the dealer and have them deal with it.
