> ## Content Index > Fetch the complete content index at: https://www.notatechguy.com/llms.txt > Use this file to discover other available public pages before exploring further. # Open-source trust signals are breaking, study finds - URL: https://www.notatechguy.com/open-source-trust-signals-are-breaking-study-finds/ - Published: 2026-08-31T22:29:30.000Z - Updated: 2026-08-31T22:29:30.000Z - Description: An arXiv preprint finds the cheap signals developers use to pick open-source dependencies are collapsing under gaming and AI-driven inflation. - Author: Marcello Babbili - Tags: Technology & AI, Google An arXiv preprint from researchers at North Carolina State University and Carnegie Mellon reviewed 252 web sources and 870 Reddit threads to answer a question every developer faces: how do you know an open-source package is safe? [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) [P⁴](https://arxiv.org/html/2608.20678v1?ref=notatechguy.com) The shortcuts everyone uses, GitHub stars, download counts, contributor activity, are collapsing under three forces at once. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The study likens the situation to Akerlof's classic lemons problem: when fabricating the appearance of trust is cheaper than building genuine trust, the whole signalling system loses its meaning, and the distance between expert recommendations and day-to-day practice only grows. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) **My read:** This is the first study I've seen that maps the full breadth of signal collapse across the open-source ecosystem rather than documenting a single attack vector. The "market for lemons" framing is an analogy, not a validated economic model, and the paper is a preprint with no peer review. But the core observation rings true: I've watched developers pick packages by star count for years, and the rise of AI-generated code and synthetic activity makes that heuristic worse, not better. What I'd watch is whether the call for mandatory cryptographic attestation gains any real traction, because voluntary security measures in open source tend to stay voluntary. ## How developers pick packages, and why it's breaking When a developer needs a library to parse JSON or handle authentication, they rarely read the source code. Instead they glance at the GitHub star count, check the download numbers on npm or PyPI, and look at whether the project has active contributors. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The study labels these "cheap trust signals", inexpensive to evaluate, and used as proxies for the real question underneath: is this code safe and maintained? [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The problem is that all three of these signals can be faked, and the cost of faking them is dropping. ## Three forces tearing the signals apart The study identifies three forces collapsing trust signals at the same time. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The first is adversarial manipulation: bad actors deliberately inflating stars, downloads, or contributor activity to make malicious packages look popular. This is not new. Prior research has documented individual cases of signal gaming. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The second is gaming that looks identical to legitimate behaviour. A maintainer who pushes trivial commits to keep a "recently active" badge is doing the same thing a bot farm does. The signal cannot tell them apart. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The third is the newest and the one the study flags as least understood: non-adversarial AI-driven inflation. As AI tools generate more code, more documentation, more pull requests, and more issues, the volume of activity around a project can surge without any corresponding increase in quality or human oversight. A package can look bustling and alive because an AI assistant filed 50 issues last week. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The study found no documented behaviour change in either corpus, Google Search results or Reddit threads, in response to this third force. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) Practitioners have not adjusted how they read signals even as the signals degrade. ## The lemons problem The paper borrows its central metaphor from George Akerlof's 1970 analysis of used-car markets, where buyers cannot distinguish good cars from bad ones, so they stop trusting any seller and the market unravels. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) In open source, the study argues, the same dynamic is taking hold. When the cost of manufacturing a trust signal falls below the cost of legitimately earning one, reliable and unreliable dependencies become impossible to tell apart. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) A developer who spends three hours auditing a package's code produces the same confidence level as one who spends three seconds checking its star count, because both signals are now unreliable. The proposed fixes are not inspiring confidence either. The study found that responses to signal collapse typically involve substituting one cheap signal for another or aggregating several signals together. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) Both approaches are already gameable. A bot that can inflate stars can inflate any proxy metric you replace them with. More damning is the gap between knowing and doing. Of the 252 Google Search sources the study reviewed, 54.6% contained advice on what practitioners should do, with no evidence of anyone actually doing it. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The ecosystem knows it has a problem. It has not changed its behaviour. ## What to do about it The study's prescription is blunt: stop relying on individual developers to verify cheap signals, because that approach is not sustainable. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) Instead, costlier signals like cryptographic attestation, where a build process is independently verified and signed, should be made mandatory so they become the default for everyone, not a voluntary choice for the security-conscious few. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) Consider a mid-sized fintech startup that pulls 200 open-source dependencies into its payment service. The lead engineer currently picks packages by scanning star counts and last-commit dates. If those signals are compromised, a malicious dependency could ride into production on the back of a faked popularity score. Cryptographic attestation would mean every package in the build chain carries a verifiable signature proving where it came from and that it was built from the claimed source. The startup does not need to trust the star count. It needs to trust the signature. This is not investment or security advice, and the study's policy recommendations are the authors' prescriptions, not industry consensus. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) But if you work with open-source dependencies, one practical step this week is to check whether your build pipeline supports SLSA (Supply-chain Levels for Software Artifacts) provenance verification, and whether your most critical dependencies publish signed build attestations. The tooling exists. Adoption does not. ## What we don't know yet This is a preprint, not a peer-reviewed paper. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The methodology relies on qualitative coding of Google Search results and Reddit threads, which may carry selection bias: Reddit over-represents certain developer communities, and Google results shift with ranking algorithms. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The 54.6% figure applies only to the 252 Google Search sources, not the combined corpus including Reddit. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The study did not empirically audit software packages or code directly; it analysed what people write about trust signals, not the signals themselves. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The "market for lemons" framing is a theoretical argument, not an empirically validated economic model in this context. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) And the call for mandatory cryptographic attestation is an author prescription, not a regulation or industry standard. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) No findings have been independently replicated. [S¹](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) The next signal: whether this paper passes peer review and whether any major package registry (npm, PyPI, crates.io) moves toward mandatory provenance attestation in the next 12 months. We'll check both claims against the registries' published roadmaps. If this was useful, subscribe for weekly analysis of the research and decisions reshaping how software gets built and trusted. --- *Sources: [S1 — The Software Supply Chain as a Market for Lemons: A Multivocal Review ](https://arxiv.org/abs/2608.20678v1?ref=notatechguy.com) · [P2 — The Software Supply Chain as a Market for Lemons: A Multivocal Review ](https://arxiv.org/html/2608.20678?ref=notatechguy.com) · [P3 — deep-diver/paper-reviewer](https://github.com/deep-diver/paper-reviewer?ref=notatechguy.com) · [P4 — The Software Supply Chain as a Market for Lemons: A Multivocal Review ](https://arxiv.org/html/2608.20678v1?ref=notatechguy.com) · [P5 — Abdrakib/ml-research-assistant](https://github.com/Abdrakib/ml-research-assistant?ref=notatechguy.com)* ## More from Not A Tech Guy - [ComfyUI hits GitHub trending at 130,000 stars](https://www.notatechguy.com/comfyui-hits-github-trending-at-130-000-stars/) - [NVIDIA's $3.5B MediaTek deal extends AI from cloud to car](https://www.notatechguy.com/nvidia-s-3-5b-mediatek-deal-extends-ai-from-cloud-to-car/) - [last30days skill hits 60,000 stars searching Reddit and X](https://www.notatechguy.com/last30days-skill-hits-60-000-stars-searching-reddit-and-x/) --- *Generated from an audited evidence pack with primary-source research. Social-media items are discussion signals, not verified facts. Nothing here is financial, legal or medical advice.* ![Corpus sources reviewed in the study](https://storage.ghost.io/c/6e/89/6e896869-22ef-4281-a213-b4c462c17cff/content/images/2026/08/chart_1824c0758b37a30705b2.png)