Skip to content

Leaklens status

Answered our latest tool-list check 22 hours ago with 2 tools. It will be marked verified after 3 successful checks in 7 days.

Answered (30 days)
1 of 1 checks
Last seen working
16 Nov, 12:16 UTC
Last commit
—
Licence
Not stated

Live checks

We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.

  • Answered
  • Needs sign-in
  • No answer
Checked (UTC)ResultResponse timeTools
16 Nov, 12:16Answered1.7 s2

Tools (2)

Read from the server on 16 Nov 2026.

check_task_leakage
Check whether coding tasks from SWE-bench-style benchmarks leaked their fix. Pass one instance ID for the full evidence, or up to 50 IDs in the queries field, as a JSON array of strings or one string separated by commas, spaces or new lines (a results file's task list), to get back which are flagged. Each task returns its tier, state and agreement, countedInHeadline, a one-clause why, a quoted sen
benchmark_leakage_summary
How leaky is a coding benchmark? Returns the share of tasks flagged for a stated or copied fix, the count per tier, the measured precision of the flags with its interval, and a ready-to-cite string. Optionally lists the flagged tasks of one repo (flaggedTasks, the headline's rule: Tier A where both checks agreed, plus Tier C) and the tasks flagged but counted apart (notCountedTasks: Tier B, Tier A