{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigja55r54dondnzyyzqaqhd4ij3np7b5jnywbnc5f235fnvvlfbki",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mkwwd7g2f4c2"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918?page=4#post_77",
  "publishedAt": "2026-05-03T09:04:07.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "Why We Built a Haskell Package Manager in Rust"
  ],
  "textContent": "AshleyYakeley:\n\n> Give me examples of Haskell packages that are bad because of AI-generated code.\n\nI don’t have any.\n\nBut I also think that’s largely besides the point. There is indication that AI assisted code is on average more buggy and less secure than entirely human written code. I’ve already linked those articles earlier in this thread, I don’t think it needs to be repeated.\n\nIt’s quite possible that all my fears are unfounded when it comes to specifically the Haskell community. And if it turns out that way, I’ll be very happy. But so far all things point to LLM slop becoming a problem.\n\nAlthough it was in rust, we already have cases where people posted their low-effort slop projects: Why We Built a Haskell Package Manager in Rust",
  "title": "How to filter out vibe-coded dependencies"
}