David Kim

General 12 min

David Kim • 21 hours ago

MOSS, JPlag, and AI Detectors Across 1,200 Obfuscated Submissions

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.

Read

General 11 min

David Kim • 2 days ago

Three Semesters of Detecting Collusion in CS1 Without Burnout

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.

Read

General 10 min

David Kim • 5 days ago

At What Renaming Threshold Do Token-Based Detectors Fail?

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.

Read

Case Studies 2 min

David Kim • 1 month ago

One Community College's Web Code Plagiarism Strategy

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%.

Read

General 8 min

David Kim • 2 months ago

How Winnowing Fingerprints Resist Variable Renaming

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.

Read

General 9 min

David Kim • 2 months ago

What Code Similarity Metrics Actually Measure in Student Work

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.

Read

General 12 min

David Kim • 2 months ago

An OSPO Lead's Map Through the GNU License Compliance Maze

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.

Read

Academic Integrity 10 min

David Kim • 2 months 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.

Read

General 7 min

David Kim • 3 months ago

How Open Source License Auditing Actually Works

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.

Read

General 5 min

David Kim • 3 months ago

Your Website's HTML Was Stolen Yesterday

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.

Read

General 7 min

David Kim • 3 months ago

The Hidden Plagiarism Your Static Analyzer Is Missing

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.

Read

General 7 min

David Kim • 4 months ago

The 83% Illusion in Your Open Source Compliance

A 2025 audit of 500 enterprise codebases revealed that 83% contained open-source components with undetected license violations or security flaws. This isn't just a legal problem—it's a direct threat to product viability and company valuation. We analyzed the data to show where compliance tools fail and what effective scanning actually looks like.

Read