Re:Lovable apps expose passport details and more than 200K p...
by fn-mote on Saturday November 14, 2026 @08:04PM
(#50502888)
> including the risk/cost of breaking a production build
If the customer is deploying (“to prod”) they need to know enough to assess their own risks of breaking their software.
I’d want to see the text of the warning to customers before having an opinion on how in/sufficient it was.
For instance, questions will arise, as to whether it's reasonable for Lovable to hand this kind of power over to a customer. And, if their software is capable of detecting vulnerabilities, but allows the customer to proceed, is that reasonably responsible behavior on Lovable's part?
Then, there are tests regarding what their customers should reasonably be expected to understand. For instance, it might be tempting to compare this to gun liability laws, wherein manufacturers can disclaim responsibility if their guns are mishandled. But, here, what is the level of knowledge required to fully understand the risks—including the risk/cost of breaking a production build? And, is it reasonable that their customer should be expected to understand?
And, this even comes down to their marketing. If they are actively selling to novice customers, with the pitch that no expertise is required, then it may prove very difficult to pin the blame on those customers.
Attorneys would likely argue that Lovable can't have it both ways—selling to amateurs, then blaming their customers for being amateurs.
Disclaimer: I once played a lawyer in a 7th grade mock court. Oh, and I've been sued.