Cited by 53Academic integrity and plagiarismSoftware Engineering ResearchTeaching and Learning Programming

Plagiarism Detection: A Tool Survey and Comparison

Open access
Martins, Vítor T., Fonte, Daniela, Henriques, Pedro Rangel, da Cruz, Daniela·2014·Schloss Dagstuhl – Leibniz-Zentrum für Informatik

Abstract

We illustrate the state of the art in software plagiarism detection tools by comparing their features and testing them against a wide range of source codes. The source codes were edited according to several types of plagiarism to show the tools accuracy at detecting each type. The decision to focus our research on plagiarism of programming languages is two fold: on one hand, it is a challenging case-study since programming languages impose a structured writing style; on the other hand, we are looking for the integration of such a tool in an Automatic-Grading System (AGS) developed to support teachers in the context of Programming courses. Besides the systematic characterisation of the underlying problem domain, the tools were surveyed with the objective of identifying the most successful approach in order to design the aimed plugin for our AGS.

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

DataCite · 10.4230/oasics.slate.2014.143

Cites

20 of 20 references verified0 citation errors · 0 not checkable

Statistics

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

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?

  • All source code plagiarism detection tools that are known to be available use only structural measures of similarity.

    “Furthermore, all known available SCPDTs implement structural measures of similarity only.”

    From Academic Source Code Plagiarism Detection by Measuring Program Behavioral Similarity (2021) · cites this paper as [8]

    Section 2.2, “Approaches” (page unavailable), distinguishes attribute-based, token-based, and structure-based methods rather than saying all tools use structural measures only. It describes token-based tools that add some structure-dependent modifications; Section 4.4 identifies Marble as using token comparison. These passages contradict the claim’s “all” and “only.” (LLM, conf=0.90)

    Checked by a reasoning model — may be wrong.

    Experimental — accuracy not yet measured
  • Every source code plagiarism detection tool proposed so far uses structural or semantic measures of similarity.

    “All known proposed SCPDTs implement structural or semantic measures of similarity.”

    From Academic Source Code Plagiarism Detection by Measuring Program Behavioral Similarity (2021) · cites this paper as [8]

    Section 2.2 (page not supplied) describes attribute-based and token-based methods as well as structure-based methods. Its examples include comparisons using code size and token hashes, contradicting the claim that all proposed tools use structural or semantic similarity measures. (LLM, conf=0.87)

    Checked by a reasoning model — may be wrong.

    Experimental — accuracy not yet measured
  • Recent literature reviews list a range of structural and/or semantic source code plagiarism detection tools but none that are behavioural, which supports the absence of comparable approaches.

    “The lack of similar approaches to SCPD is supported by the recent literature reviews [8], [9] that identify various structural and/or semantic SCPDTs, however, fail to identify any behavioural SCPDTs.”

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Cites

Flagged first, then by citations

1 of the 21 references couldn’t be matched to a known paper.

Research works printed but not linked: 3

  1. Aleksi Ahtiainen, Sami Surakka, and Mikko Rahikainen. Plaggie: GNU-licensed source code plagiarism detection engine for Java exercises. In Proceedings of 6th Koli Calling Intern. Conference on Comp. Ed. Research, pages 141-142, New York, USA, 2006. ACM.
  2. Dick Grune and Matty Huntjens. Het detecteren van kopieën bij informatica-practica. Informatie, 31(11):864-867, 1989.
  3. Michael J. Wise. YAP3: Improved detection of similarities in computer program and other texts. In SIGCSEB: SIGCSE Bulletin, pages 130-134. ACM Press, 1996.

Cited by

Sorted by citations

Authors
Martins, V. T., Fonte, D., Henriques, P. R., & da Cruz, D.
Affiliations
University of Minho (PT)
Venue
Schloss Dagstuhl – Leibniz-Zentrum für Informatik
Publisher
Schloss Dagstuhl – Leibniz-Zentrum für Informatik
Published
2014
OpenAlex
W2096498787
Cited by
53
References
21
Citations by year
2025: 1 · 2024: 7 · 2023: 3 · 2022: 1 · 2021: 6 · 2020: 5 · 2019: 6 · 2018: 5 · 2017: 8 · 2016: 6 · 2015: 5
FWCI
17.66
Type
journal article
Language
en
Open access
Locations
  • DROPS (Schloss Dagstuhl – Leibniz Center for Informatics) (submittedVersion, cc-by)
  • Portuguese National Funding Agency for Science, Research and Technology (RCAAP Project by FCT) (submittedVersion, other-oa)
  • Portuguese National Funding Agency for Science, Research and Technology (RCAAP Project by FCT) (submittedVersion, cc-by-nc-nd)
  • OASIcs : OpenAccess Series in Informatics (cc-by)
Funders
Fundação para a Ciência e a Tecnologia (PEst-OE/EEI/UI0752/2014)
Topics
  • Social Sciences › Safety Research › Academic integrity and plagiarism
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Computer Science Applications › Teaching and Learning Programming
Keywords
software plagiarism detection, plagiarism detection software, tool comparison, source code plagiarism, automated grading, programming education

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