Sample report. Every name and number is invented.
Ottoline Featherstone
Well belowLicenceAssessed work at Fernbrook Systems, Q2 2026. Personal training is not counted here and never reaches a team report.
- Submissions
- 4
- Findings caught
- 4 of 9
- Catch rate
- 44%
- Median score
- 47.5 against a pass mark of 80
Against a frontier model
How a frontier model scored on the same challenges, given the same changes and marked against the same correct answers, with no hints and no walkthrough. The model is not named: these figures are invented for this sample.
- This person
- 48 of 100
- The model, on the same challenges
- 58 of 100
- Difference
- -10 points
Both figures are out of 100 over the 4 challenges of theirs that a published run covers, so they are only compared on work the model has actually done.
Score over time
Every attempt in the order it was made, oldest on the left, against the pass mark.
What they catch and what they miss
The best and worst of this person's own results by weakness category. It is their own detail, not an aggregate, so no minimum cohort applies. The whole breakdown is in the table below.
Strongest
- Cryptography67% caught2 found of 31 missed
Weakest
- Secrets25% caught1 found of 43 missed
By CWE category
What this reviewer catches and misses, by weakness family.
| Category | Caught | Missed | Catch rate |
|---|---|---|---|
| Secrets | 1 | 3 | 25% |
| Cryptography | 2 | 1 | 67% |
| Data exposure | 1 | 1 | 50% |
By language
The same breakdown by the language of the codebase reviewed.
| Language | Caught | Missed | Catch rate |
|---|---|---|---|
| Go | 1 | 3 | 25% |
| Ruby | 3 | 2 | 60% |
Every attempt
Newest first. Times are in UTC.
| Challenge | Score | Grade | Caught | Took | Submitted |
|---|---|---|---|---|---|
Statement references a customer can count up tallylinechallenge 2 | 50 | Needs work | 1/2 | 14 min | 23 Jun 2026, 10:15 UTC |
A ledger signature checked after the write tallylinechallenge 1 | 60 | Needs work | 2/3 | 37 min | 22 Jun 2026, 05:15 UTC |
A token left in the sample environment file shipwrightchallenge 2 | 0 | Needs work | 0/2 | 35 min | 21 Jun 2026, 00:15 UTC |
A deploy key printed into the build log shipwrightchallenge 1 | 45 | Needs work | 1/2 | 32 min | 19 Jun 2026, 19:15 UTC |