KudozPR rewards from GitHub activity
  • Overview
  • Campaigns
  • CRE executions
  • My rewards
  • New campaign
Repositories
  • token2049-decentralizing/core
    425
  • token2049-decentralizing/valid-palindrome
    28
  • token2049-decentralizing/two-sum
    24
Checking APIcre-runner.fly.dev
  1. CRE executions
  2. cb234617…
/

Execution cb234617Completed

Preview run for token2049-decentralizing/valid-palindrome#2 in Leetcode bug fix challenge #2, started 2 hours ago.
PR historyGitHub
Score
61/ 100
Eligibility
Not eligiblepreviews never pay
Reward
0 USDCnot settled
Duration
30s

Score breakdown

Evidence35 × 40% = 14.0Code review60 × 30% = 18.0Issue fit96 × 30% = 28.8
total 61 · min 50

Evidence

35 / 100 · 40%
  • Linked issue25/25
    #1
  • CI0/25
    no completed checks

Timeline

  1. QueuedOct 7, 2026, 16:29
  2. RunningOct 7, 2026, 16:29
  3. CompletedOct 7, 2026, 16:30

Workflow request

{
  "event": "opened",
  "head_sha": "2bee4a2105eb8f98c60e607c01c5768470397f78",
  "pr_number": 2,
  "repository": "token2049-decentralizing/valid-palindrome",
  "campaign_id": "d9e9a4ac-0e53-48ca-b835-4c70a9a785d5"
}
Execution ID
cb234617-92b8-4bf9-9462-40a5ee353cb1
Event
Opened / pushed (preview)
Author
@9teMare
Paid to
Previews don't pay
Payout tx
—
Commit
2bee4a2
Webhook
560d1330-c26c-11f1-9abb-29921d264f3d
Approval
0/20
no approving review
  • Tests0/20
    no test files changed
  • Diff size10/10
    +3 / -0 lines
  • Code review

    60 / 100 · 30%
    • Correctness30/40
    • Tests0/25
    • Code quality20/25
    • Security10/10

    Issue fit

    96 / 100 · 30%
    • Issue relevance48/50
    • Value28/30
    • Scope20/20

    Eligibility

    • ✕Merged
    • ✕CI passedoptional
    • ✓Linked issue
    • ✓Min score61 / 50

    Where points were lost

    • Code review · TestsNo test was added or modified anywhere in the diff, so the claimed fix is unverified by any executable check.solve.py:11-13
    • Code review · CorrectnessThe new guard is behaviour-preserving rather than a real fix: the inner skip loops are already bounded by left < right, so left can never exceed right and the produced output is identical with or without these lines (including the '.,' example in the issue, which already returned True).solve.py:11-13
    • Code review · Code qualityThe early break duplicates the loop's existing termination condition, adding indirection to a hot two-pointer loop without documenting why the redundant guard is needed.solve.py:11-13
    Evaluation hash
    0xd9ee17a664a00a2be1ece647966aea861d520ef8ce66cabfef58a998516df279
    Policy hash
    0x97470949bbd676b3122a662cacef59519693168255b7f1716284b5b142a8cb68
    Runner
    080d6d9a597198