David works on the scanning pipeline and API that power Codequiry checks at scale, from ingestion to results delivery.
General
4 min
David Kim
•
1 week ago
A technical deep-dive into how modern plagiarism checkers spot code lifted from the open web. We walk through crawling, token-based fingerprinting, and matching algorithms that survive renaming and refactoring, with real examples and a look at where tools like MOSS fall short.
General
12 min
David Kim
•
2 weeks ago
A deep-dive comparison of MOSS, JPlag, Dolos, and hybrid detectors on deliberately obfuscated student Java code. Token-based algorithms catch most refactoring, but AI-generated obfuscation is changing the game — and combining similarity checks with AI detection is the only reliable way to stay ahead.
General
11 min
David Kim
•
2 weeks ago
When you teach 400 students each semester, “check the MOSS output” stops being a casual Friday task and becomes a logistical nightmare. After three iterations of the same introductory Java course, I’ve settled on a repeatable workflow that catches collusion without sacrificing evenings, weekends, or relationships with honest students. Here’s exactly how the pipeline works, what tools sit where, and where Codequiry finally closed the gap I was losing sleep over.
General
10 min
David Kim
•
2 weeks ago
Most CS instructors trust MOSS to catch code copying — but how much renaming actually breaks it? This step-by-step guide shows you how to run a controlled experiment, measure the exact threshold where token-based similarity collapses, and see why a multi-stage engine that combines tokens with AST fingerprinting catches what MOSS misses.
Case Studies
2 min
David Kim
•
1 month ago
When intro programming students at a mid-sized community college were copying entire code snippets from Stack Overflow and GitHub, the department needed a scalable detection solution. By integrating Codequiry’s web-source matching into their grading pipeline, they reduced surface-level copy-paste incidents by 40% in a single semester while cutting manual review time by 60%.
General
8 min
David Kim
•
2 months ago
Winnowing fingerprinting is a powerful technique for detecting code plagiarism that survives variable renaming, refactoring, and cosmetic changes. This case study examines how the algorithm works, where it succeeds, and where it falls short compared to AST-based approaches.
General
9 min
David Kim
•
3 months ago
Not all code similarity is plagiarism, and not all plagiarism is caught by string matching. This article breaks down the three major detection techniques—AST comparison, token-based analysis, and algorithmic fingerprinting—and explains what each one actually reveals about student submissions.
General
12 min
David Kim
•
3 months ago
Navigating the tangled web of GNU license compliance across thousands of repositories isn't an academic exercise—it's a daily operational challenge. This profile of a senior OSPO lead reveals the tools, triage workflows, and legal nuance that keep enterprise products out of litigation.
Academic Integrity
10 min
David Kim
•
3 months ago
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.
General
7 min
David Kim
•
3 months ago
Open source license compliance is more than a legal checkbox; it's a critical engineering workflow. This guide walks through the concrete steps of a codebase audit, from initial inventory to resolving conflicts. You'll learn how to map dependencies, interpret license obligations, and build a sustainable compliance practice.
General
5 min
David Kim
•
3 months ago
The code that makes your website unique is a prime target for theft. From entire HTML templates to critical JavaScript functions, web plagiarism is rampant and often invisible. This guide shows you where to look and how to fight back, protecting your intellectual property and your competitive edge.
General
7 min
David Kim
•
4 months ago
Static analysis tools scan for bugs and smells, but they are blind to a pervasive form of intellectual property theft. Our analysis of 1,200 codebases reveals that 41% contain code plagiarized directly from Stack Overflow, GitHub gists, and commercial tutorials—code often carrying restrictive licenses. This is a legal and integrity blind spot that traditional scanners cannot see.