{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreialhu3pjsj6mgqixk6qvit6o3k3hxkleod3jqmclpuyfchn6bjcf4",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjgvk7fcylv2"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918?page=3#post_43",
  "publishedAt": "2026-04-14T07:16:35.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "Really, it’s less a problem about vibecoding than careless & sloppy code. The Hackage rating mechanism is kind of underused, and given that the Haskell community tends to have good standards in terms of code quality, encouraging people to use it more might help mitigate the issue. Ratings might correlate well with the quality, and given that a lot of people in the comments share your sentiment about AI, it will also filter out projects that are mostly AI slop. You could just filter out packages with low rating with some script, regardless of whether it’s a bitrotten, vibecoded, or just someone’s pet project that’s unlikely to be any good.",
  "title": "How to filter out vibe-coded dependencies"
}