{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiffq3e7t3o3rxcl3borauyrnqihtdz7hwvtf2cuxi7zpr3dz5se5q",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjc35haccyc2"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918?page=2#post_37",
  "publishedAt": "2026-04-12T09:36:25.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "FPtje:\n\n> What if my software gets serious vulnerabilities or bugs because of ai slop dependencies? What if hackage becomes overloaded with slop and we can’t find the human programmed packages anymore? What if the quality of previously good packages goes down the drain because someone in the dependency tree doesn’t understand their code? What if library intent/cognitive/technical debt go through the roof and Haskell becomes a super buggy and unsafe language?\n\nThose are all great questions, and I’d rather have the answers.\nI just don’t care if another spike of this negligent attitude and sloppy maintainership comes from the Eternal September, Stack Overflow, or AIs. We are our own supply-chain attackers",
  "title": "How to filter out vibe-coded dependencies"
}