# VIBE-Pro leaderboard

Coding benchmark

> Every figure below is reproduced as its upstream source published it: nothing is modelled, estimated, interpolated or converted. `Unavailable` means no source published the value — it is never a zero. Each value carries its evidence state and the date it was observed.

Page: https://modelchoice.dev/leaderboards/benchmarks/coding-vibe-pro

Every model the catalog carries a published VIBE-Pro value for, ranked by that value.

## Benchmark record

| Field | Value |
| --- | --- |
| Category | Coding |
| Measure | Repository-level implementation benchmark |
| Tasks | Full project delivery tasks |
| Difficulty | End-to-end software delivery |
| Published by | [MiniMax M2.7: Early Echoes of Self-Evolution](https://www.minimax.io/news/minimax-m27-en) |

A repo-level code generation and full-project delivery benchmark spanning web, mobile, and simulation-style implementation tasks.

## VIBE-Pro ranking

1 model with a published VIBE-Pro value, ordered by that value, highest first. Models the source has not scored on this benchmark are not listed — they are unmeasured, not last.

| Rank | Model | Provider | Repository-level implementation benchmark | Evidence |
| --- | --- | --- | --- | --- |
| 1 | [MiniMax M2.7](https://modelchoice.dev/models/minimax-m2-7) | MiniMax | 55.6 | Observed 2026-11-21 · source benchlm:models |

Rows are ordered by the value the source published, highest first. The source does not state whether a higher value is the better result, so this document does not either: for a benchmark that measures a rate of failure, read the table from the bottom.
