verl-project/verl-omni - Open Source PR Review Scorecard

Multimodal RL training framework for diffusion & omni models

C-Rank Grade: S (Elite) - 72/100

External PR Merge Rate: 69%

Response Time: -

First Timer Success: 62%

Frequently Asked Questions

Is verl-project/verl-omni welcoming to first-time open-source contributors?

verl-project/verl-omni has a recorded first-timer success rate of 62.1%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in verl-project/verl-omni respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 71.9 C-Rank™ score (S Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 71.9 places verl-project/verl-omni in the S tier.

What is the external contributor pull request merge rate for verl-project/verl-omni?

The external contributor pull request merge rate for verl-project/verl-omni is 68.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in verl-project/verl-omni?

verl-project/verl-omni currently has 21 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

verl-project
verl-project/verl-omniS•Elite1.3k
GitHub
Back to Explorer
verl-project

verl-project/verl-omni

1,250
Active (30d)S•Elite(72/100)Python

Multimodal RL training framework for diffusion & omni models

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
9.2/10
Patience Score
9.0/10
Nitpick Rate
25%

Highly welcoming maintainers in verl-project/verl-omni. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
68.7%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
62.1%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
48 core
Highly collaborative maintainer core
Diagnostic Health HUD
68.7%
Merge Gauge
62.1%
1st-Timer
Community Vibe46/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for verl-project/verl-omni
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/verl-project/verl-omni)](https://getmerged.abhishekco.de/verl-project/verl-omni?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Call for contributions: RL & distillation algorithms for diffusion & omni post-training We'd love your help bringing new post-training algorithms into verl-omni. The shortlist below is all published work with runnable reference code, and each fits the loss registry and recipe structure already in the repo — so a contribution is a focused PR, not a research project. Treat it as suggestions, not a closed menu — other algorithms are welcome too, and a short RFC is a good way to start. If one of these catches your eye, please comment here first so we can coordinate. 1. DGPO — Direct Group Preference Optimization (ICLR 2026) Paper: arXiv 2510.08425 · Code: Luo-Yihong/DGPO Extends DPO from pairs to whole groups and drops the policy gradient entirely, which unlocks deterministic ODE samplers — the paper reports ~20× faster training than existing diffusion RL. 2. TDM-R1 — RL for few-step models with non-differentiable rewards (ICML 2026) Paper: arXiv 2603.07700 · Code: Luo-Yihong

📅 Opened Oct 8, 2026💬 10 comments
Quality: 90/100Contribute

Dashboard RFC: take MiniMax-H3 from working LoRA recipes to production-scale training. Land incremental PRs; do not treat this as one change. Foundation already on main: T2VA #347/#368/#383, FL2VA #396/#401/#448, Ref2VA #458/#464/#485, V1 sync T2VA/FL2VA #501, FLOPs/MFU #548. 1. Pipelines Official H3 tasks are t2va / fl2va / ref2va. There is no H3 ti2va; image-conditioned generation is FL2VA (first / last / first+last keyframes). Task DiffusionNFT FlowGRPO V1 sync GPU NPU T2VA ✅ ✅ ✅ ✅ FlowGRPO only FL2VA ✅ ✅ ✅ ✅ ❌ Ref2VA ✅ ✅ ✅ ✅ ❌ Gaps: Ref2VA V1 sync (and later separate_async once checkpoint-engine sync exists). Reference-aware rewards for Ref2VA (CLAP/ImageBind do not measure reference fidelity). FL2VA / Ref2VA NPU (optional; T2VA FlowGRPO NPU already exists). Default recipes already cover first-frame FL2VA; last / first+last are data-path supported via frame_mode. 2. VeOmni actor backend (default candidate) VeOmni is already wired in

📅 Opened Sep 18, 2026💬 5 comments
Quality: 70/100Contribute

1. Summary This RFC proposes adding DiffusionNFT (direct-preference forward-process RL) support for the BOOGU-Image model family, covering both text-to-image (Boogu-Image-0.1-Base) and instruction-guided image editing (Boogu-Image-0.1-Edit). Currently, BooguImagePipeline only supports policy-gradient FlowGRPO (algorithm="flow_grpo"). While FlowGRPO performs well, it requires collecting reverse-SDE trajectories and log-probabilities across all denoising steps, incurring high rollout host memory and network transfer overhead. DiffusionNFT trains from final clean latents ($x_0$) using a forward-process objective, enabling: Significant rollout memory reduction: Omits trajectory latent/logprob caching, slashing rollout-to-actor tensor payload by ~10–20×. Native deterministic ODE generation: Rollout uses native Euler/ODE inference without stochastic SDE perturbation, avoiding likelihood drift. High sample efficiency for image editing: Provides stable preference optimization for both text

📅 Opened Sep 7, 2026💬 5 comments
Quality: 90/100Contribute

Feature request Build the DMD2 FSDP engine and offline trainer integration for the Qwen-Image MVP in #519, using the loss/config work in #520 and the concrete adapter/acceptance work in #543. Following cr-gao's review, replace the general role-runtime/controller/executor design with a concrete DMD2 integration. Draft PR #546 implements this reusable runtime slice; the concrete Qwen adapter and recipe are reviewed separately under #543. Motivation DMD2 needs differentiable sampling, detached fake-stage samples and independent student/fake optimization, not another Ray lifecycle or arbitrary role/transport framework. Adapt the existing worker/engine's single-active-optimizer assumptions rather than treating DMD2 as PPO replay or an OPD request. Only DMD2 distribution-only is in scope. Original DMD, GAN, causal Wan and Self-Forcing are not prerequisites. Proposed structure main_diffusion / existing task and resource-pool setup -> DistributionMatchingRayTrainer(BaseRayDiffusionTrainer)

📅 Opened Sep 4, 2026💬 2 comments
Quality: 70/100Contribute

Feature request Implement the DMD2 loss and standalone DMD configuration for the Qwen-Image MVP in #519. This replaces this issue's former generic-controller/immutable-plan scope, following the review of #545. This is a CPU-verifiable foundation for the concrete engine/trainer and Qwen integration in #535/#543. It does not introduce a production trainer shell, a four-recipe registry, or claim runnable training by itself. Existing #545 code still follows the previous design until it is updated; prior passing tests do not certify this revision. Motivation Separate algorithm identity, shared mathematics, and execution: Original DMD (dmd, deferred) combines distribution matching with paired teacher-trajectory regression. DMD2 (dmd2, MVP) removes that paired regression and trains the student against frozen real-score and trainable fake-score predictions with two-timescale optimization. Fake-score denoising MSE is not original DMD's paired generator-regression term. A class named DMDLoss re

📅 Opened Sep 3, 2026💬 0 comments
Quality: 70/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for verl-project/verl-omni

When evaluating whether to contribute to verl-project/verl-omni, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of verl-project/verl-omni acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 68.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to verl-project/verl-omni

01

Is verl-project/verl-omni welcoming to first-time open-source contributors?

verl-project/verl-omni has a recorded first-timer success rate of 62.1%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 71.9 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 71.9 places verl-project/verl-omni in the Elite tier.

04

What is the external contributor pull request merge rate for verl-project/verl-omni?

The external pull request merge rate is 68.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in verl-project/verl-omni?

Yes, verl-project/verl-omni currently has 21 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for verl-project/verl-omni are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.