{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreif7dimrv3dbbod6a76aqp4r7erkyzaphs37zhrew5d257yzzidkrm",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mkswujcd2nf2"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918?page=3#post_59",
  "publishedAt": "2026-05-01T18:17:21.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "requires uploaders to declare whether AI was used to produce a package and in what measure"
  ],
  "textContent": "hasufell:\n\n> I also had some more expressive solutions in mind, where e.g. hackage could have a label that authors themselves can add as a declaration, such as `vibe-coded`.\n\nThere is precedent for this. Luanti’s ContentDB requires uploaders to declare whether AI was used to produce a package and in what measure.\n\nAnd from what I’ve seen packages are being tagged accurately. People have said that LLM users are just going to lie and mark their packages as not generated, but I think that’s just a minority of people that’s projecting their attitude on others.",
  "title": "How to filter out vibe-coded dependencies"
}