Clones: what is that smell?
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Unrestrained code synthesis risks the unnoticed introduction of code clones, a long-standing maintainability concern.
“One clear risk of unrestrained code synthesis is the unnoticed introduction of code clones - a long-standing maintainability concern, even if empirical studies are not conclusive on their severity (Rahman et al. 2012 ).”
From Echoes of AI: Investigating the downstream effects of AI assistants on software maintainability (2026) · cites this paper as Rahman et al. 2012
The citation lists haven’t been fetched yet
References 49 · Cited by 132
- Authors
- Rahman, F., Bird, C., & Devanbu, P.
- Affiliations
- University of California, Davis (US)
- Microsoft (United States) (US)
- Corresponding author
- Rahman, Foyzur
- ORCID
- Bird, Christian
- Venue
- Empirical Software Engineering
- Published
- 2011-12-24
- Volume
- 17
- Issue
- 4-5
- Pages
- 503-530
- ISSN
- 1382-3256 (ISSN-L)
- 1573-7616
- OpenAlex
- W1973650376
- Cited by
- 132
- References
- 49
- Citations by year
- 2026: 2 · 2025: 5 · 2024: 4 · 2023: 7 · 2022: 3 · 2021: 9 · 2020: 6 · 2019: 7 · 2018: 14 · 2017: 14 · 2016: 11 · 2015: 8 · 2014: 14 · 2013: 16 · 2012: 7
- FWCI
- 36.79
- Type
- journal article
- Language
- en
- Open access
- closed
- Licence
- www.springer.com/tdm (tdm)
- Locations
- Empirical Software Engineering (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
- Keywords
- code clones, code smells, defect proneness, open source software, software maintenance
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
