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
12 min
Rachel Foster
·
2 weeks ago
A department ran a web-source scan on 412 intro Python submissions and got 61 hits, 23 of which were noise. This is the eight-step workflow they built afterward, from normalizing LMS exports and budgeting GitHub's code search rate limit to ranking matches by token count instead of percentage and assembling an evidence packet that survives an appeal.
General
13 min
Rachel Foster
·
3 weeks ago
License detection spent twenty years matching strings against license texts and missing the code underneath them. The algorithms that fixed it came out of plagiarism research, not legal tech. A look at what changed after 2003, and what the AI boom reopened.
General
17 min
Rachel Foster
·
4 weeks ago
Most CS departments teach students to cite what they copy but never to read the license attached to it. This reported guide walks through the licenses that actually show up in student repositories, the four failure modes that recur in grading, and a provenance rubric that separates academic honesty from legal obligation.
General
12 min
Dr. Sarah Chen
·
1 month ago
A mid-size CS department got 41 similarity flags from a single assignment and no written policy for what any of them meant. This is the calibration exercise they ran, the AI cluster that confused everyone, and the starter-file mistake that produced 61 false 100% matches.
General
12 min
Rachel Foster
·
1 month 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
8 min
Rachel Foster
·
1 month 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
11 min
Dr. Sarah Chen
·
2 months 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.
General
8 min
Rachel Foster
·
2 months ago
AI code detectors are producing false positives on the most ordinary submissions in CS1: code that looks the same because the assignment required it. This reported piece examines the data, the workflow changes instructors are making, and why combining AI detection with structural similarity reduces the error rate.
General
4 min
Marcus Rodriguez
·
2 months ago
A three-semester case study at Briarwood University tracked 14,000 Python assignments through four AI code detectors. The result: false positive rates from 4% to 9% overall, spiking to 23% on common algorithmic patterns. This article breaks down the data, the code patterns that trigger false flags, and a practical workflow for balancing detection with fairness.
General
7 min
Dr. Sarah Chen
·
3 months ago
We cut similarity rates from 43% to 7% in a Data Structures course not by policing harder but by rewriting the assignments themselves. Here's what worked, what broke, and where detection tools like Codequiry still earn their keep.
General
11 min
Alex Petrov
·
3 months ago
When Riverside University’s CS department ran an AI detector across 300 CS2 assignments alongside MOSS, they discovered a new layer of academic integrity challenges. The case study reveals what they found, how they calibrated thresholds, and why combining AI detection with source-code fingerprinting changed their grading workflow.
General
11 min
Marcus Rodriguez
·
3 months ago
Most plagiarism detectors rely on token streams, which break down as soon as students rename variables, reorder statements, or extract methods. We map the precise failure points, walk through AST-based recovery techniques, and show how fingerprinting fills the gaps that tree comparators leave behind. A must-bookmark deep‑dive for any CS educator or engineering lead who has watched suspect code sail right through a token‑only scanner.