This entirely depends on the product. If it’s your own personal blog, then for sure no need to read the code, but a change in a banking architecture would be irresponsible to not have an understanding of the actual code change.

> If it’s your own personal blog, then for sure no need to read the code,

I can off the top of my head think of at least three ways in which being careless with the code powering "your personal blog" could have real consequences. Suppose it has a bug which allows unauthenticated users to manage your pages, or even worse remote code execution. Then it could be used as a jumping-off point to attack other systems, for instance by turning it into a C&C server for some malware. It could be used in a "watering hole attack" against your readers. Or someone could edit the blog articles to make it appear that you said something you didn't.

"Not reading the code" is irresponsible for any software exposed to the global network.

Yes, vibe coding is perfectly acceptable if it is coupled with financial and penal liability of the authors of the program for any damages caused by that program, so if they choose to use it they must be willing to bet on its suitability.

In case of damages, vibe coding should be an aggravating circumstance, i.e. gross negligence.

When the use of a program cannot have any nefarious consequences, obviously vibe coding is fine. However, I do not use many such applications.