← All sample reports Synthetic sample code only (F18) — no real student or candidate work.
ai-code-detector · screening reportpage 1 / 4

Screening report · sample

mixed-review-09 — weak and ambiguous signals

Job IDdemo_job_mixed_signal
Submitted2026-09-12 16:40 UTC
Files12 files · 1,906 lines total · Python (9) · JavaScript (3)
Engine versioncodebert-ft-0.1.0
RetentionSample report — not stored, nothing to delete
Note This score estimates the likelihood that code was AI-generated. It is a screening signal, not proof of AI use. False positives and false negatives occur. Always review flagged work with the author and follow your institution’s or company’s policies before taking any action.
ai-code-detector · screening report demo_job_mixed_signal · screening signal, not proof — review flagged work with its author

Sheet 2 · Summary — per-file scores, sorted

summarypage 2 / 4

Per-file scores, highest first

Start your review at the top of this table. A high score means "review this first" — nothing more.

#FileLinesAI-likelihood scoreFlagged lines
1file_utils.py132
58
44–47
2helpers.py88
51
12–14
3week3_starter.py64 — not scored —
4app.js176
42
90–92
5recursion_lab.py97
35
—
…7 more files—lower signal—
0–6 · lower signal
7–13 · mixed signal
14–100 · stronger signal
ai-code-detector · screening report demo_job_mixed_signal · screening signal, not proof — review flagged work with its author

Sheet 3 · File detail — side-by-side evidence

file detail · week3_starter.pypage 3 / 4

week3_starter.py

— AI-likelihood score
Flagged code
1def add(a, b):
2 return a + b
3
4def main():
5 print(add(2, 3))
Why these segments were flagged
overall
Too short and too close to the course starter template for a useful signal. The report declines to score this file — review it by hand if it matters.

Signal groups referenced: naming patterns · comment density · structural predictability · edge-case handling.

ai-code-detector · screening report demo_job_mixed_signal · screening signal, not proof — review flagged work with its author

Sheet 4 · How to use this report + archival record

how to use this reportpage 4 / 4

How to use this report

This report is a record of a screening step. It is not a finding of misconduct, and it is not a basis for a grade penalty or a hiring decision on its own.

  1. Ask the author to explain the flagged snippets — people who wrote the code can usually walk through it.
  2. Ask them to extend or modify the flagged code on the spot, with a small change in requirements.
  3. Compare with the author's earlier work before drawing any conclusion.

Archival record

Report generated2026-09-12 16:40 UTC
Engine versioncodebert-ft-0.1.0
RetentionSample report — synthetic code, no personal data.
Methodology/accuracy
Note This score estimates the likelihood that code was AI-generated. It is a screening signal, not proof of AI use. False positives and false negatives occur. Always review flagged work with the author and follow your institution’s or company’s policies before taking any action.
ai-code-detector · screening report demo_job_mixed_signal · screening signal, not proof — review flagged work with its author

Run this on your own files — sign up free →