While vibe coding seems like the easy way to make things, there is a problem.

One that non-programmers don’t recognise.

Because they’re not versed in the art of programming.

Using AI to create websites is fine.

Generally not too much security risk there as long as there are no forms on the page.

Using AI to create music, images, or video is also not a security issue.

There might be a copyright issue, but that’s going through the courts at the moment.

But when it comes to writing apps with vibe coding there is a security issue.

Unless the vibe coder thinks to ask the AI what security problems there are, they’ll never know or fix them.

But I’m seeing a trend that is a serious problem.

Vibe coding extensions for your web browser.

The issue is that when you use any of these extensions that didn’t come from the app store the browser has to be left in developer mode.

That leaves the front door of your web browser wide open.

It’s not possible to install an extension from a file you or someone else creates without being, and staying, in developer mode.

I have created an extension for myself that is in the app store.

It runs happily in my web browser with no security risk.

At this stage I haven’t seen any exploit targeting browsers in developer mode, but because any extension can be loaded in this mode the risk is there.

It’s a similar risk to the old “turn off your anti-virus software to install this software” request that used to happen.

I never did.

If it couldn’t install with the anti-virus software running, I didn’t need that program.

It’s the same with these extensions.

If you have to stay in developer mode, you don’t need it.

To see my extension click the link.

https://link.ckv.to/open-in-background

There are 469 installs, one 1-star review, and I don’t care because it works for me, and it’s not for sale.

Regards,
​​​​​​​Brent.