The DOI matches its DataCite record; 11 of the 11 references it cites were found in a registry or an index.
Finding Plagiarisms among a Set of Programs with JPlag
Open accessAbstract
JPlag is a web service that finds pairs of similar programs among a given set of programs. It has successfully been used in practice for detecting plagiarisms among student Java program submissions. Support for the languages C, C++ and Scheme is also available. We describe JPlag’s architecture and its comparsion algorithm, which is based on a known one called Greedy String Tiling. Then, the contribution of this paper is threefold: First, an evaluation of JPlag’s performance on several rather different sets of Java programs shows that JPlag is very hard to deceive. More than 90 percent of the 77 plagiarisms within our various benchmark program sets are reliably detected and a majority of the others at least raise suspicion. The run time is just a few seconds for submissions of 100 programs of several hundred lines each. Second, a parameter study shows that the approach is fairly robust with respect to its configuration parameters. Third, we study the kinds of attempts used for disguising plagiarisms, their frequency, and their success.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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?
The source backs part of the claim, not all of it — or backs it for a different population, condition or comparison.
In the citing paper
“By converting source code into ASTs, the structural logic of the program is preserved, rendering the detection mechanism robust against superficial textual changes.”
From Automatic Code Plagiarism Detection using AST and Machine Learning (2026) · cites this paper as [2]
Experimental — accuracy not yet measuredThe cited source says what the claim attributes to it.
In the citing paper
“As the tokens abstract from the code, the comparison is inherently resilient against particular obfuscation attacks, such as renaming, retyping, or obscuring constant values [37].This particularly includes immunity against all lexical [16] attacks.”
From Detecting Automatic Software Plagiarism via Token Sequence Normalization (2024) · cites this paper as [37]
The cited source says what the claim attributes to it.
In the citing paper
“According to Prechelt et al. [37], the extracted token sequence”
From Detecting Automatic Software Plagiarism via Token Sequence Normalization (2024) · cites this paper as [37]
The cited source says what the claim attributes to it.
In the citing paper
“Mossad demonstrates its effectiveness against various plagiarism detectors, including MOSS [1], Sherlock [16], and JPlag [36,37].”
From Detecting Automatic Software Plagiarism via Token Sequence Normalization (2024) · cites this paper as [37]
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
The publisher hasn’t deposited this paper’s reference list.
Research works printed but not linked: 1
- [9]9. J. A. W. Faidhi and S. K. Robinson. An empirical ap- proach for detecting program similarity within a university programming environ- ment. Computers and Education, 11(1):11-19, 1987.
Cited by
CP-Miner: finding copy-paste and related bugs in large-scale software code
Li, Z., Lu, S., Myagmar, S., & Zhou, Y. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.28 · Cited by 610
“Index Terms—Software analysis, code reuse, code duplication, debugging aids, data mining.”
BackgroundA Survey of Automated Assessment Approaches for Programming Assignments
Ala-Mutka, K. M. (2005) · Computer Science Education · doi:10.1080/08993400500150747 · Cited by 546
“MOSS is based on document fingerprinting (Schleimer, Wilkerson, & Aiken, 2003) and JPLAG uses string tokenization with sub-string pattern matching (Prechelt, Malpohl, & Philippsen, 2002).”
MethodGPLAG: detection of software plagiarism by program dependence graph analysis
Liu, C., Chen, C., Han, J., & Yu, P. S. (2006) · Proceedings of the 12th ACM SIGKDD international conference on Knowledge discovery and data mining · doi:10.1145/1150402.1150522 · Cited by 422
“We spent two hours plagiarizing it such that both Moss and JPlag were confused.”
BackgroundMethodInfluentialAttack of the Clones: Detecting Cloned Applications on Android Markets
Crussell, J., Gibler, C., & Chen, H. (2012) · Lecture Notes in Computer Science · doi:10.1007/978-3-642-33167-1_3 · Cited by 270
“Examples of this approach include JPLAG [38], Winnowing [40] and MOSS [18].”
MethodA comparison of code similarity analysers
Ragkhitwetsagul, C., Krinke, J., & Clark, D. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9564-7 · Cited by 122
Metadata
- Authors
- Malpohl, G., Prechelt, L., & Philippsen, M.
- Affiliations
- Karlsruhe Institute of Technology (DE)
- ORCID
- Lutz Prechelt
- Venue
- Verlag der Technischen Universität Graz
- Publisher
- Verlag der Technischen Universität Graz
- Published
- 2002
- OpenAlex
- W4292014584
- Semantic Scholar
- 3b40ae4486e8f455331692e07a06a46b25728f68
- Cited by
- 56
- References
- 0
- Citations by year
- 2026: 4 · 2025: 4 · 2024: 10 · 2023: 4 · 2022: 6 · 2021: 3 · 2020: 10 · 2019: 4 · 2018: 2 · 2017: 4 · 2015: 1
- Type
- data paper
- Language
- en
- Open access
- green
- doi.org
- Locations
- TUGraz OPEN Library (Graz University of Technology)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Social Sciences › Education › Academic integrity and plagiarism
- Physical Sciences › Computer Science › Computer Science Applications › Teaching and Learning Programming
- Keywords
- plagiarism detection, JPlag, software plagiarism, code similarity, source code plagiarism, Java programs
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Finding Plagiarisms among a Set of Programs with JPlag. https://app.cochat.ai/papers/10.3217/jucs-008-11-1016
- The paper
- Malpohl, G., Prechelt, L., & Philippsen, M. (2002). Finding Plagiarisms among a Set of Programs with JPlag. Verlag der Technischen Universität Graz. https://doi.org/10.3217/jucs-008-11-1016
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.