Expert insights on AI code detection and academic integrity
As AI coding assistants become ubiquitous, learn how institutions are adapting to detect AI-generated code and maintain educational standards.
Codequiry Editorial Team
·
Jan 5, 2026
Stay ahead with expert analysis and practical guides
General
15 min
Dr. Sarah Chen
·
1 day ago
Dependency scanners read manifests. They cannot see the 300 lines someone pasted into a file with the header deleted. This piece walks through what actually constitutes an open source license violation, why SBOM tooling goes blind at exactly the wrong moment, and how provenance checks catch copied code before counsel does.
General
12 min
David Kim
·
1 week ago
An AI detection score is a signal, not a verdict. This is the four-stage triage I borrowed from a fintech incident pipeline to decide which alerts deserve a conversation, which deserve a case file, and which deserve to be closed.
General
15 min
Alex Petrov
·
1 week ago
Two Python submissions scored 4% against each other and in the 70s against a Java gist from 2017. Cross-language plagiarism is the fastest-growing blind spot in academic integrity because translation destroys the text while preserving everything that matters. Here's what survives a translation, what detectors actually see, and where the false positives come from.
General
10 min
David Kim
·
1 week ago
Line diffing under-reports copied code and over-reports similar-looking code. Here's what token normalization and AST fingerprinting actually compare, where each one breaks, and how to wire both into a CI pipeline or an academic submission workflow.
General
12 min
Rachel Foster
·
1 week ago
Renaming variables and swapping a for loop for a while loop defeats simple text matching, but it rarely defeats structural comparison. This report walks through the obfuscation ladder, the algorithms that climb it, and the published detection rates behind the claims, including the cases where every engine still misses.
General
11 min
Priya Sharma
·
2 weeks ago
A public research university ran AI code detection as part of its grading workflow for a full academic year: eleven assignments, three courses, 4,118 submissions. The interesting number isn't the 3.8% that ended in a finding. It's the roughly two flagged files that got cleared for every one that held up, and what the department changed because of it.
General
13 min
Alex Petrov
·
2 weeks ago
A Java submission and a Python submission looked nothing alike, but they were the same algorithm translated line by line. This is the story of how cross-language code plagiarism detection actually works, where it catches translated code, and where it still fails.
General
8 min
Rachel Foster
·
3 weeks ago
A University of Missouri-St. Louis instructor spent two decades watching code similarity tools change shape. The gaps between each generation of detection explain why instructors now run peer, web, and AI checks side by side.
General
8 min
Dr. Sarah Chen
·
3 weeks ago
A CS professor traces how AI-generated code detection grew out of MOSS-era token fingerprints, code stylometry, and a broken similarity assumption. The piece explains how modern detectors work, where they still stumble, and why stacked peer, web, and AI signals make the most defensible academic workflow.
General
11 min
Rachel Foster
·
3 weeks ago
A public university ran MOSS, JPlag, and Codequiry against the same 214 Python submissions, plus 30 AI-generated files. The tools disagreed on nearly a quarter of flagged cases. One combined approach changed how instructors review code.
General
9 min
Marcus Rodriguez
·
4 weeks ago
A student renames every variable and converts for loops to while loops. MOSS still flags 94%. This guide builds a minimal winnowing detector in Python 3.11 so you can see exactly why code plagiarism detection algorithms survive refactoring. We then look at where the approach breaks and how AST matching fills the gap.
General
11 min
Dr. Sarah Chen
·
4 weeks ago
One CS department's switch from a single similarity tool to a layered detection workflow changed what they could see in student code. Peer copying, web sources, and AI-generated submissions each required different signals, and combining them revealed more than any one check alone.