An interesting detail missing here is that there are two types of scans: “quick scans” and “deep scans.” Quick scans run automatically whenever a user publishes a project, while deep scans must be triggered manually -- except for enterprise customers.

https://docs.lovable.dev/features/security#built-in-security...

We are moving this feature to all paid tiers soon. I agree that scanning on schedule needs to be available to everyone.

> If your users are less technical then I think it is irresponsible to allow them to make choices that would compromise security and the data of others.

Counterpoint: HN about the iPhone. FWIW, I agree with the statement above, but also suggest a developer account opening up developer flags is a reasonable gate.

(Not sure how else to avoid all the "developers" clamoring for non-public betas of iOS bricking their iPhones, as the same audience that would flip a bunch of dev toggles if available to everyone like developer mode in Safari then scream how Apple should have done more to protect them when their bank account is emptied.)

But not needing to know what you're doing as far as programming goes != not needing to know what you're doing as far as compliance/legal responsibility. Someone using a tool like this still needs to run their operation in a sane manner. Like, how much responsibility does Loveable shoulder here? We don't blame a car manufacturer for most car crashes. They, of course, try to design their cars to be as safe as possible, but the fact that they endeavor to make a safe car doesn't make it explicitly their fault if I'm driving blindfolded and careen off a cliff.

This is something that makes me roll my eyes... seeing people online talking about how everyone can just make their own version of w/e software now. As though running a software business is simply a matter making the computer screen light up in a particular way.