Detect plagiarised and similar code across trillions of code sources on the web See what's new

Category

Academic Integrity

Best practices for fair, defensible plagiarism workflows and honest assessment in computer science courses.

Teaching Code Attribution Before Students Write a Single Line Academic Integrity 11 min
Emily Watson Emily Watson 1 day ago

Teaching Code Attribution Before Students Write a Single Line

Too many CS students treat code from Stack Overflow, GitHub, or AI tools as free for the taking. Teaching attribution as a core skill from the first assignment reduces plagiarism and builds professional habits. This article walks through concrete strategies, assignment patterns, and detection workflows that make attribution part of the learning process.

Contextualizing Programming Problems to Reduce Cheating Academic Integrity 10 min
Priya Sharma Priya Sharma 1 week ago

Contextualizing Programming Problems to Reduce Cheating

Instead of fighting plagiarism after submissions arrive, you can design assignments that are inherently resistant to copying. By embedding unique, student-specific context into problem statements, you make it obvious when code has been copied and also harder for AI tools to produce a correct answer. This article covers concrete techniques—parameterized test cases, local data imports, and narrative hooks—that real universities have used to cut similarity rates by over 40%.

How to Design Assignments That Resist Code Plagiarism Academic Integrity 9 min
Alex Petrov Alex Petrov 1 week ago

How to Design Assignments That Resist Code Plagiarism

Simple changes to assignment design—unique interfaces, randomized test harnesses, and automated similarity checks—drastically reduce code plagiarism. This guide walks through six concrete tactics with real code examples and grading workflows.

How Automatic Grading Evolved From Scripts to Integrity Pipelines Academic Integrity 9 min
Alex Petrov Alex Petrov 1 month ago

How Automatic Grading Evolved From Scripts to Integrity Pipelines

A retrospective on automatic grading in computer science education—from shell scripts comparing output strings to modern platforms combining unit tests, static analysis, and code similarity detection. What we gained, what we lost, and why integrity pipelines matter more than ever.

Teaching Students to Write Attribution Comments in Group Work Academic Integrity 10 min
David Kim David Kim 1 month ago

Teaching Students to Write Attribution Comments in Group Work

Attribution comments are a simple but powerful tool for teaching code integrity in collaborative programming projects. This article explains how to implement them effectively, what to include, and how they transform group work from a plagiarism minefield into a learning opportunity.

The Assignment That Broke a University's Honor Code Academic Integrity 7 min
James Okafor James Okafor 2 months ago

The Assignment That Broke a University's Honor Code

A third-year data structures course at a prestigious university became ground zero for a cheating scandal that traditional tools missed. The fallout wasn't about catching individuals—it was about discovering a broken culture. This is the story of how they rebuilt their standards from the ground up.

The Assignment That Taught Students How to Cheat Academic Integrity 6 min
Emily Watson Emily Watson 2 months ago

The Assignment That Taught Students How to Cheat

A well-intentioned "cheat-proof" programming project at a top-tier university inadvertently became a masterclass in sophisticated plagiarism. The fallout revealed a critical gap in how we teach and assess code integrity, forcing a department-wide reckoning on what originality really means in software.

Your Students Are Hiding Plagiarism in Plain Sight Academic Integrity 9 min
Rachel Foster Rachel Foster 3 months ago

Your Students Are Hiding Plagiarism in Plain Sight

Plagiarism detection isn't just about matching code. Savvy students are using sophisticated obfuscation techniques—dead code injection, comment spoofing, and false refactoring—that fool standard similarity checkers. This guide reveals their methods and provides a tactical workflow to uncover the deception, preserving academic integrity in advanced courses.

Your Students Are Copying Code You Can't See Academic Integrity 11 min
Marcus Rodriguez Marcus Rodriguez 3 months ago

Your Students Are Copying Code You Can't See

A student submits a perfectly functional binary search tree. The logic is flawless, but the variable names are gibberish and the structure is bizarrely convoluted. It passes MOSS with flying colors. This is obfuscated plagiarism, the most sophisticated form of academic dishonesty in computer science. We're entering an arms race where simple token matching is no longer enough.

The Code Your Students Stole Is Legally Toxic Academic Integrity 8 min
Rachel Foster Rachel Foster 3 months ago

The Code Your Students Stole Is Legally Toxic

A student copies a slick React component from a GitHub repo with a strict GPL license. They submit it. They graduate. The original author finds it. Now the university's software IP is contaminated. This isn't just cheating—it's a legal time bomb. We explore the hidden world of license violation through academic plagiarism and how to scan for it before it's too late.

The 37% Problem in Your Intro to Java Course Academic Integrity 2 min
James Okafor James Okafor 3 months ago

The 37% Problem in Your Intro to Java Course

A 2023 multi-university study found that 37% of introductory programming submissions showed signs of unauthorized collaboration, undetected by traditional string-matching tools. The culprit isn't copy-paste—it's structural plagiarism, where students share solutions and rewrite them line-by-line. Here’s how algorithms that compare Abstract Syntax Trees are exposing this silent epidemic.

The Code That Broke a University's Honor Code Academic Integrity 3 min
Rachel Foster Rachel Foster 3 months ago

The Code That Broke a University's Honor Code

A routine data structures assignment at a major university revealed a plagiarism ring involving over 80 students. The fallout wasn't just about cheating—it exposed fundamental flaws in how institutions detect, define, and deter source code copying. This is the story of what broke, and what every CS department needs to fix before the next scandal hits their inbox.