{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidbp6znew5b2zrbzlxmjawrl24l5mscoql3m7zdsrwu3y5kvameye",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjbnq2zfrc22"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918?page=2#post_25",
  "publishedAt": "2026-04-12T05:42:26.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "Ok, but you know the answer - you can’t tell if a dependency is “StackOverflow” programmed, so how are you going to determine if they are vibe-coded, which by your definition is a more sophisticated variant?\n\nhasufell:\n\n> That means they created three types of debts:\n\nI have created all three of these types of debts by hand as well. I’ve also done “StackOverflow programming” and used LLMs without any of them. This seems like a poor correlation at best.\n\nhasufell:\n\n> My topic has a very specific question. If you don’t want to contribute to solving the problem, then you don’t have to engage in this discussion.\n\nYour question is specifically “how to avoid vibe-coded deps” but you won’t say what vibe-coding even is, with enough details for us to answer the question. I am trying to contribute a solution, but you’re being too vague.",
  "title": "How to filter out vibe-coded dependencies"
}