-
Notifications
You must be signed in to change notification settings - Fork 320
Home
JPlag finds pairwise similarities among a set of multiple programs. It can reliably detect software plagiarism and collusion in software development. All similarities are calculated locally, and no source code or plagiarism results are ever uploaded to the internet. JPlag supports a large number of programming and modeling languages. JPlag does not merely compare bytes of text but is aware of programming language syntax and program structure and hence is robust against many kinds of attempts to disguise similarities (obfusction) between plagiarized files.
JPlag is typically used to detect and thus discourage the unallowed copying of student exercise programs in programming education. But in principle, it can also be used to detect stolen software parts among large amounts of source text or modules that have been duplicated (and only slightly modified). JPlag has already played a part in several intellectual property cases where it has been successfully used by expert witnesses.
Just to make it clear: JPlag does not compare to the internet! It is designed to find similarities among the student solutions, which is usually sufficient for computer programs.
Originally, JPlag was developed in 1996 by Guido Mahlpohl and others at the chair of Prof. Walter Tichy at Karlsruhe Institute of Technology (KIT). It was first documented in a Tech Report in 2000 and later more formally in the Journal of Universal Computer Science. Since 2015 JPlag is hosted here on GitHub. After 25 years of its creation, JPlag is still used frequently in many universities in different countries around the world.
Download the latest version of JPlag here. If you encounter bugs or other issues, please report them here.
Use JPlag via the CLI to analyze your set of source codes. You can display your results via jplag.github.io. No data will leave your computer! More usage information can be found here.
JPlag is released on Maven Central, it can be included as follows:
<dependency>
<groupId>de.jplag</groupId>
<artifactId>jplag</artifactId>
<version><!--desired version--></version>
</dependency>
In case you depend on the legacy version of JPlag, we refer to the legacy release v2.12.1 and the legacy branch. Note that the legacy CLI and report UI are different and provide fewer features.