IMO, it goes against 'self-hosted' too. Self-hosting for your own data, control of it, and handling of it. Self-hosting to learn new things and scratch your own itch for a niche product. AI vibe coding doesn't have any of that. Literally an _idea_ that someone else implements and you the 'coder' don't really have any control or understanding of.

Why would I want to take ownership of that for my own security?

it’s respectful of everyone’s time if the “vibe coded disclaimer” is at the TOP of the readme, not the bottom. Why bury that in the fine print?

It’s also a very good indicator of how invested the author is in the repo. Is this a throwaway weekend project? Is it their “baby” so to speak? Should i even bother asking the author a question if i run into an issue, after all, they didn’t write any of the code so…