A brief look into the Codequiry database:
50M+ files of public code: GitHub repositories, Stack Exchange answers, the CodeParrot dataset, and code earlier checks found on the web. Every check runs against this index. Nobody's submission is ever added to it. Search it the way you would search a repo: a function name, an error string, or a line from a student's file.
quicksort. Search above to query the live index.
What's in the index
Results above come from four sources, all of it public code. Each result is labelled with the one it came from.
| Source | What it is | Shown as |
|---|---|---|
| GitHub | Source files from public repositories, including course repos and the solution repos students find when they search an assignment title. | owner/repo/path |
| Stack Exchange | Code from answers on Stack Overflow and the other Stack Exchange sites. | site/question path |
| CodeParrot | An open dataset of source code collected from GitHub. It is a snapshot, so it still holds files that were later edited or deleted from the original repo. | repo/path |
| Web source | Public code that earlier checks found on the web: gists, Software Heritage, Sourcegraph and other pages. A check adds the sources it finds once a week; the code your students submit is never added. | file name |
This page is a text search
Type quicksort and you get files that contain the word quicksort. It is a quick way to see whether the code from an assignment is already sitting in a public repo or an old answer.
A check compares whole files
When you run a check, every submission is fingerprinted by structure, so renamed variables, reordered functions and rewritten comments still match. It is compared against this index, 427B+ web sources, and every other submission in the class.
Run a check on a real assignment. Yearly plans for institutions.