The problem is not the vibecoding, it is the release of a public facing internet app that is not a day old, hence it is impossible to know if it has security issues. He is supposedly a security engineer and he RELEASES a repo with less than a day old? how do you know it is secure? Again, this is something that will interact with the open internet.
replyGatekeeping would be "do not write vibecoded apps for yourself", which is not the case here, this is releasing code for the public in an irresponsible manner.
I mean, every repo was 13 hours at some point. can't hardly get security updates unless others can see and review it.
replyI mean, I feel you... there's no way I'm running it when it's this new... I'll let others spend their tokens probing it and check it out in a month... no shade in the dude for releasing it, but anyone who has it running right now inside their network... I hope nothing bad happens.
Also I do not want to rely on an app that can vanish any day. Established app are way less suceptible to that.
replyGood thing it’s open source, so the user can verify the code themselves.
reply