{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigyy7mqh5myoppkbojpngmjx6ww54k25wvw6j2f5l6wexae5yxrem",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mk3u7ok3la32"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918?page=3#post_53",
  "publishedAt": "2026-04-22T14:23:58.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "GitHub - hasufell/vibecode-scanner · GitHub",
    "here"
  ],
  "textContent": "I started this project: GitHub - hasufell/vibecode-scanner · GitHub\n\nIt’s very early stage and the major limitation is how to find the git repo of a cabal project (I utilize `cabal get --source-repository=head`). Because without that, you can’t do any interesting checks anyway.\n\nExample:\n\n\n    $ cabal --verbose=0 run vibecode-scanner -- scan hackage hatter\n    {\n        \"scannedAgents\": [\n            {\n                \"commits\": 371,\n                \"directories\": [],\n                \"files\": [],\n                \"name\": \"Claude Code\"\n            }\n        ],\n        \"scannedPkg\": \"hatter\"\n    }\n\n\nThe agents definition is here. I plan to allow to extend/overwrite that with a Dhall config.",
  "title": "How to filter out vibe-coded dependencies"
}