Expert insights on AI code detection and academic integrity
Stay ahead with expert analysis and practical guides
General
8 min
Dr. Sarah Chen
·
2 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
·
2 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
11 min
David Kim
·
3 weeks ago
A DevSecOps lead's field notes on running AI-generated code detection as a merge request gate in GitLab CI, with the exact YAML, thresholds, and audit trail decisions that survived a fintech rollout.
General
11 min
Dr. Sarah Chen
·
3 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.
General
8 min
David Kim
·
3 weeks ago
Most vendor code passes unit tests and static analysis. It fails provenance checks. This is the exact merge gate I run in a fintech CI pipeline: Codequiry's plagiarism and AI scans wired into GitHub Actions, with thresholds, evidence review, and a failure policy.
General
10 min
James Okafor
·
3 weeks ago
A practical, code-level guide to batch-scanning Python files for web-sourced code. We walk through token normalization, fingerprinting, uploading to Codequiry, interpreting web match URLs, and stacking an AI check on flagged files. Built for CS professors auditing assignments and engineering managers verifying contractor code.
General
10 min
Dr. Sarah Chen
·
3 weeks ago
A CS professor ran 1,200 Java submissions through three AI code detectors. Codequiry caught 94% of known AI files and flagged only 3.5% of pre-LLM human code, while the other tools posted two to three times that false positive rate. The full numbers and methods are below.
General
9 min
Priya Sharma
·
4 weeks ago
Across 41,000 student submissions at a large public university, an 85% token-level similarity score between two students predicted confirmed misconduct 92% of the time in introductory courses. This guide walks through the exact calibration workflow, score distributions by language, and tiered review thresholds that worked for my assessment team.
General
8 min
Rachel Foster
·
1 month 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
6 min
Rachel Foster
·
1 month ago
Set up an automated code plagiarism detection pipeline in GitHub Actions using Codequiry's REST API. Follow precise steps to write a workflow YAML and a Python script that submits student code, receives similarity scores, flags suspicious pushes, and optionally detects AI-generated code. Includes threshold tuning, result interpretation, and false positive handling.
General
12 min
Priya Sharma
·
1 month ago
A three-semester analysis of 4,100 CS1 submissions shows why a 70% similarity score means different things in Python, Java, C++, and JavaScript. I break down percentile thresholds, boilerplate effects, false positives, and how to pair similarity checks with AI detection.
General
10 min
Priya Sharma
·
1 month ago
Most plagiarism checkers only compare submissions against each other, so a Stack Overflow snippet with renamed variables sails through. We break down how web source matching uses token and AST fingerprints to catch code copied from Stack Overflow, GitHub, and tutorials, and show a Java example where refactoring did not hide the source.