{
  "id": 20370733,
  "title": "\"Proof of use\" as a requirement for open source contributions?",
  "url": "https://urgent.news/2026/11/16/proof-of-use-as-a-requirement-for-open-source-contributions",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-16T22:25:45.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://lobste.rs/s/ki1l5r/proof_use_as_requirement_for_open_source"
  },
  "original_language": "en",
  "account": "As an open source maintainer, the author encounters a large number of AI-generated pull requests. While some have genuine value, many address edge cases that rarely occur in real life. The maintainer is now experimenting with a requirement for contributions: proof of use. Contributors must demonstrate that their project, which depends on the maintainer's software, is being used in practice. This proof can be in the form of an existing open source project that imports the maintainer's code (showing the git history) or a clear description explaining how the maintainer's software is utilized in a closed-source production environment. The primary goal is to ensure that only contributions from individuals who genuinely rely on the software are considered, while filtering out the noise generated by projects like OpenClaw or green square farms on GitHub that use large language models to generate submissions. The author is curious about the opinions of the lobste.rs community on this approach.",
  "summary": "As an open source maintainer, I get a lot of AI slop PRs. Some of these have genuine value. Most address edge cases that almost never occur in real life. It's not that they're not fixing real problems, it's that they're fixing problems that nobody is ever likely to encounter. I'm experimenting with \"proof of use\" as a requirement for submissions. Specifically, you need to show me that your…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}