Sample report

See the work, not just the promise.

We are preparing a complete, ungated Dokima report from a pinned open-source codebase. The target and method will be disclosed so you can judge the result.

Report statusBenchmark run in preparation

We will publish the complete report here when the run and independent mapping are ready.

A fair demonstration

Known outcome. Unknown to Dokima.

The sample will use a historical commit from a real open-source project, selected immediately before one or more known security issues were fixed. Dokima will review that commit without being given the advisory or expected answer.

After the run, we will map the report against the known issues and separate any additional findings. A missed issue stays a miss; an unsupported claim does not become a success because it sounds plausible.

What we will disclose

01

Exact source

Repository, branch and pinned commit reviewed by Dokima.

02

Review setup

Dokima version, runner, model and relevant configuration.

03

Run details

Review duration and runner usage or cost where it can be reported fairly.

04

Complete outcome

Full report, known-issue mapping, misses and additional findings.

What you will be able to inspect

The same report structure your team receives.

  • Plain-English issue descriptions
  • Technical evidence and affected scope
  • Severity, confidence and verification status
  • Attack path and practical outcome
  • Detailed and plain-English remediation
  • Finding status and review annotations

While the sample is being prepared

Evaluate Dokima against a codebase your team already understands.

Request a full-product trial for your engineering team. No payment card required.