Prilog

PUBLIC RESULTS / OPEN-SOURCE CONTRIBUTIONS

Accepted code changes.
Evidence you can inspect.

Explore fixes from Prilog's open-source contribution program. Inspect 39 merged fixes and 86 open PRs awaiting review or merge, with direct links to the upstream code and discussion.

39Merged upstream
86Open PRs awaiting outcome
125Merged or open PRs
30Repositories with merged fixes

Campaign snapshot: 39 merged · 86 open (including 1 draft) · 38 closed without merge · 3 unverified. The cards show merged and open PRs; download all 166 records for other outcomes. Open means awaiting a maintainer outcome, and may include existing review feedback. Daily checks refresh the snapshot when metadata changes; no overall success rate is calculated.

THE PUBLIC RECORD

Merged fixes and work awaiting review.

How to read these results ↗

Showing all 125 merged or open PRs; merged fixes first.

WHAT THE RECORDS ESTABLISH

Code, review, and an upstream outcome.

The linked GitHub records confirm PR state and merge dates. They do not independently establish elapsed fix time, CI completion, how much a human edited, or how much of each change Prilog produced.

A merged contribution is not an endorsement of Prilog by the project. We contribute open-source fixes at no charge as a way to give back to the community.

Read three detailed examples ↗

A SEPARATE EVALUATION

91.2% SWE-bench Verified

Prilog reports 456 of 500 issues resolved in a feedback-guided evaluation. The method retains 413 earlier passing patches and regenerates 87 selected cases.

The self-reported submission is open for review as of October 26, 2026. It is not pass@1 or an official leaderboard rank.

Read the method and artifacts ↗

TRY YOUR OWN ISSUE

The next result should be useful to your team.

Connect one repository, bring a real failure, and inspect the proposed change.

Follow the quickstart ↗