Stack Overflow data: 79% of devs prioritise source attribution for AI training
New survey data reveals strong developer concern regarding source attribution, impacting firms licensing Q&A archives to model builders.

Key points
- % of respondents consider source attribution important for AI models.
- Developers are heavily engaged with AI tools despite reservations.
- Licensing Q&A archives to model builders faces scrutiny over attribution.
A recent survey conducted by Stack Overflow indicates that source attribution is a critical concern for the majority of developers using artificial intelligence tools. According to The Register, 79 per cent of respondents stated that knowing the origin of AI-generated content matters significantly. This finding has direct implications for companies that license Stack Overflow’s question-and-answer archives to organisations building large language models.
How it unfolded
- Stack Overflow released survey results detailing developer attitudes towards AI integration.
- The Register reported that 79 per cent of participants prioritised source attribution.
- The data highlights tension between AI adoption and trust in model judgment.
Who is affected
Organisations that license technical Q&A archives to AI model builders are directly affected by these findings. The survey suggests that while developers are hooked on AI technology, they remain skeptical about the judgment and reliability of the outputs. This skepticism is tied closely to transparency regarding data sources. Companies relying on licensed data for training must now account for this high demand for attribution among the primary user base of their training data.
The fix
No technical patch or software update addresses these survey findings, as they reflect user sentiment rather than a software vulnerability. The issue concerns data licensing practices and user trust rather than code defects. Consequently, there is no immediate fix to apply. Stakeholders must navigate these concerns through policy adjustments and transparent communication regarding data usage rather than technical remediation.
What to do and how to stay safe: Stack Overflow
- Review current data licensing agreements to ensure they address source attribution requirements explicitly.
- Monitor developer community feedback regarding AI tool transparency and data provenance standards.
- Implement internal guidelines for verifying the origin of AI-generated code or content used in projects.
- Assess how lack of attribution in training data might impact user trust in your AI products.
Step-by-step guide: Patch Management: Eight Questions Answered for Stability
General security guidance from the Malware Brief newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What percentage of developers care about source attribution?
According to the survey, 79 per cent of respondents consider source attribution important.
Do developers trust AI judgment completely?
No, the survey indicates developers are hooked on AI but are not totally sold on its judgment.
Who is impacted by these findings?
Companies licensing Q&A archives to model builders are impacted, as attribution matters to users.



