Code Intelligence Hub

General 9 min

Emily Watson · 3 weeks ago

K-gram Fingerprinting for Source Code Similarity Analysis

K-gram fingerprinting is the backbone of modern code plagiarism detection. This step-by-step guide walks through tokenization, k-gram generation, hashing, winnowing, and comparison — the exact pipeline used by MOSS and Codequiry. Includes Python code examples, algorithmic tradeoffs, and real-world scaling numbers.

Read →

Tutorials 7 min

Alex Petrov · 3 weeks ago

Automated Code Similarity Checks in a CI Lab Pipeline

Setting up automated code plagiarism and similarity checks inside a CI pipeline cuts manual grading time and catches copying that individual reviewers miss. This practical guide walks through the architecture, tooling choices, and honest tradeoffs of running MOSS, JPlag, or Codequiry’s API on every lab push.

Read →

General 1 min

Emily Watson · 3 weeks ago

How Abstract Syntax Tree Comparison Detects Restructured Code

Abstract syntax tree (AST) comparison is a powerful technique for detecting code plagiarism that has been restructured through variable renaming, method reordering, and whitespace changes. This article explains how AST comparison works, its strengths and limitations, and when to combine it with token-based methods for best results.

Read →

General 8 min

Dr. Sarah Chen · 3 weeks ago

Why Some CS Departments Are Moving Beyond Moss for Plagiarism Detection

Riverdale State University’s computer science department spent years relying on Moss to catch plagiarised assignments. But as student work grew more sophisticated — combining copied web code, heavy refactoring, and AI-generated fragments — the department realised token-based similarity alone was no longer sufficient. This case study covers how they transitioned to a multi-tool detection pipeline.

Read →

General 10 min

Marcus Rodriguez · 4 weeks ago

What Code Fingerprinting Is and How It Catches Plagiarism

Source-code fingerprinting is the core technique behind every major plagiarism detection tool, from MOSS to Codequiry. This guide explains how it works at the algorithm level, shows you how to interpret its output, and offers practical strategies for designing assignments that resist its limitations.

Read →

Case Studies 9 min

Emily Watson · 4 weeks ago

How One Bootcamp Built a Code Originality Pipeline

When CareerDevs Academy scaled from 30 to 200 students per cohort, their manual code review process couldn't keep up with plagiarism and improper code reuse. Here's how they built a tiered originality pipeline combining static analysis, similarity detection, and educational intervention — and what other programs can learn from their approach.

Read →

General 11 min

Emily Watson · 1 month ago

How Static Analysis Catches Plagiarized Code Before It Ships

Plagiarism isn't just a classroom problem. When code from Stack Overflow, GitHub repos, or contractor deliverables enters your production codebase without proper attribution, you risk license violations, IP disputes, and technical debt. This guide shows how static analysis tools detect copied code before it ships, using token matching, AST comparison, and dependency scanning.

Read →

General 8 min

David Kim · 1 month 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 →

Academic Integrity 9 min

Alex Petrov · 2 months ago

How Automatic Grading Evolved From Scripts to Integrity Pipelines

A retrospective on automatic grading in computer science education—from shell scripts comparing output strings to modern platforms combining unit tests, static analysis, and code similarity detection. What we gained, what we lost, and why integrity pipelines matter more than ever.

Read →

Tutorials 10 min

Alex Petrov · 2 months ago

Building a Source Code Provenance Pipeline for Contractor Deliverables

When contractors deliver source code, verifying originality and license compliance is critical. This guide walks through building an automated provenance pipeline that checks for code similarity, license violations, and proper attribution before accepting deliverables into your codebase.

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 →