I think it is the other evidence that it is vibe coded

• Brand new account
• Dev only responds to non-technical or feel-good comments
• other commenters have pointed to AI teltale vibe coding syntax signs in many of the files
• Claude extra files in early commits and changing gitignores to do it.

Advertised Vibe coded projects absolutely are by default bad and here is why:

• Developers do not understand what they have built, so can't debug it beyond "Claude, fix this"
• Vibe coded projects are easy-come, easy-go very often abandoned (73% of the vibe projects on flathub, and those are the people who thought far enough to decide putting it on flathub was worth it)
• developers can't answer any questions on security when the app will be handling credentials, be hosted on a server, or attach to some sort of live service -> absolutely gaping security hole that you just have to cross you fingers that Claude didn't do another "oops, you are completely right to push back,1500 common attack vectors were left open and you are now part of a CSAM botnet, do you want me to fix it?"

If someone wants to make small scripts, one-off test firmware for a home project, writing test cases, design reviews, boilerplates, etc... Are arguably good usecases.

Vibe coding an ongoing software service is almost always a hard no-go and statistically will be abandoned and unupdated, leading to even more security and usability issues.

I didn't say it did, but also "vibe coding" is a fairly new term that does not have a strict consistent definition anyway.

Subjective, but I'd also trust it less to not have serious mistakes, such as deleting everything in your home directory. Or unexpectedly running insecure HTTP server on all interfaces.
Or perhaps just having a temporary file stored on SSD which gets written to way too much, causing great wear to the drive. Or slow memory leaks.

Just things a human would likely think of.

anecdotally, I've built a lot of projects and abandoned them because I ran out of time. With an LLM to reduce the input effort I actually think I would've maintained them longer.

do you have a source which backs up what you're claiming?

Guy writes you a free tool and all they can do is look a gift horse in the mouth.

Misunderstanding.
Main point here was that the person should disclose they used LLMs if they did, and to what degree. So, like, one line of text in the README. Similar to how food products list allergens - might be important to some people.

Linus Torvalds also has some vibe-coded stuff for private use that he published. But he also made that clear:

Also note that the python visualizer tool has been basically written by vibe-coding. I know more about analog filters -- and that's not saying much -- than I do about python. It started out as my typical "google and do the monkey-see-monkey-do" kind of programming, but then I cut out the middle-man -- me -- and just used Google Antigravity to do the audio sample visualizer.

I'd like to add my perspective.

I'm not very anti-AI, I use a locally run model to help me write code (especially boring stuff).

For me it's mostly about "is it worth the time to package this thing in Nixpkgs, add it to my config, and get used to how it works?"

And for vibecoded projects, even if they work now, the answer is "probably not"; more specifically it's "let's look if it's alive in a year, if I'm still interested".

As such, I really appreciate when people add a disclaimer so that I don't have to go look at the code only to be disappointed - I also appreciated it back in the day when someone said "this is my first real project" or something, for similar reasons.

And secondly it's a question of trust. If the author doesn't disclose such basic things about the way the project has been developed, and in fact avoids answering when asked directly, what other potential problems could there be semi-hidden in the codebase?

yep, that's basically my thought.

"if you can't say something nice, don't say anything at all" is what my momma taught me.

if it's malicious that's one thing, if it's free and open source who gives a rats ass how it was made.

oh no your free thing you didn't pay for gets abandoned? why don't you take up the reins?

just feels like asking a lot of people and giving them nothing in return