unslothai/unsloth - Open Source PR Review Scorecard

Local UI to run and train LLMs and diffusion models. Supports GGUF, MLX, Qwen3.8, DeepSeek-V4, MiniMax-H3, Gemma 4, FLUX and more.

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

External PR Merge Rate: 69%

Response Time: -

First Timer Success: 56%

Frequently Asked Questions

Is unslothai/unsloth welcoming to first-time open-source contributors?

unslothai/unsloth has a recorded first-timer success rate of 56.5%. 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 unslothai/unsloth 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 68.0 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 68.0 places unslothai/unsloth in the S tier.

What is the external contributor pull request merge rate for unslothai/unsloth?

The external contributor pull request merge rate for unslothai/unsloth is 68.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in unslothai/unsloth?

unslothai/unsloth currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

unslothai
unslothai/unslothS•Elite77.7k
GitHub
Back to Explorer
unslothai

unslothai/unsloth

77,668
Active (30d)S•Elite(68/100)Python

Local UI to run and train LLMs and diffusion models. Supports GGUF, MLX, Qwen3.8, DeepSeek-V4, MiniMax-H3, Gemma 4, FLUX and more.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
35%

Collaborative maintainer environment in unslothai/unsloth. Reviews community pull requests with focus on project quality.

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.5%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
215 core
Highly collaborative maintainer core
Diagnostic Health HUD
68.5%
Merge Gauge
56.5%
1st-Timer
Community Vibe44/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Hi, I think the How to Run Local LLMs with OpenAI Codex doc is outdated or incomplete for current Codex CLI versions: https://unsloth.ai/docs/basics/codex Summary I tested the local Codex + Unsloth + llama.cpp flow on macOS using an under-10GB Unsloth model and was able to get it working, but not with the doc steps as written. The main problem is not the model itself. The issue is that current Codex CLI sends a /v1/responses tool payload that llama.cpp rejects unless a compatibility layer is added. The page already hints at this with: {"error":{"code":400,"message":"'type' of tool must be 'function'","type":"invalid_request_error"}} But the page still reads like the local Codex flow works directly, and the fallback it mentions (wire_api = "chat") is no longer a practical current solution. What I tested I used: Codex CLI v0.123.0 llama.cpp built locally Unsloth model: unsloth/Qwen3.6-27B-GGUF quant: Qwen3.6-27B-UD-IQ2_XXS.gguf (under 10GB) macOS on Apple Silicon I verified: llama-ser

📅 Opened Apr 23, 2026💬 14 comments
Quality: 30/100Contribute

Well notebook fails in Kaggle is due to three Colab-specific dependencies. i think that one of the best way to use unsloth studio is in kaggle. but after a lot of experiments that fails i just think that the best guys how can do something about that are the unsloth team. who can do like the awesome work that you do in colab but in kaggle. and thank you so much for the things that you do for the community and OSS.

📅 Opened Apr 10, 2026💬 2 comments
Quality: 30/100Contribute

Hi, I’m currently using Unsloth Studio to fine-tune unsloth/ Whisper Large v3, and I have a question regarding dataset ingestion. My dataset consists of audio files stored privately on AWS S3 along with their corresponding transcriptions. I’d like to know whether Unsloth Studio supports direct integration with S3 (e.g., via bucket paths, IAM roles, or signed URLs) during the dataset upload step. At the moment, I’m unsure if there is a built-in way to connect an S3 bucket or if all data must first be downloaded locally to the instance. Could you clarify if this feature exists, is planned, or if there is a recommended workaround for securely using private S3-hosted audio datasets within Unsloth Studio? Thank you for helping..

📅 Opened Mar 23, 2026💬 6 comments
Quality: 30/100Contribute

Currently I can find amd64 images available. However, training on aarch64 clusters seems tricky, and building xformers from source can be annoying. An aarch64 image would be appreciated for convenience.

📅 Opened Mar 11, 2026💬 4 comments
Quality: 15/100Contribute

Feature Request: Idefics3 Architecture Support Summary Requesting native Unsloth support for the Idefics3 architecture, which would enable optimized fine-tuning of models like IBM Granite Docling VLM (258M params) — a high-performing document understanding model. Why This Matters Granite Docling VLM achieves 87.7 on DocVQA with only 258M parameters (vs. the original Idefics3-8B at 74.0). It's Apache 2.0 licensed and increasingly used for document conversion (PDFs, scans, slides → structured output). Unsloth support would make fine-tuning this model significantly faster and more memory-efficient, opening it up to consumer GPUs. Architecture Analysis Granite Docling VLM (and all Idefics3 models) uses Idefics3ForConditionalGeneration. Its components map closely to things Unsloth already supports: Component Idefics3 / Granite Docling Unsloth Status Vision Encoder SigLIP2-base-patch16-512 SigLIP supported in other VLMs (LLaVA, etc.) Language Model Granite 165M (Llama 3-based) L

📅 Opened Feb 19, 2026💬 5 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 unslothai/unsloth

When evaluating whether to contribute to unslothai/unsloth, 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 unslothai/unsloth acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 68.5% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to unslothai/unsloth

01

Is unslothai/unsloth welcoming to first-time open-source contributors?

unslothai/unsloth has a recorded first-timer success rate of 56.5%. 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 68.0 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 68.0 places unslothai/unsloth in the Elite tier.

04

What is the external contributor pull request merge rate for unslothai/unsloth?

The external pull request merge rate is 68.5%. 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 unslothai/unsloth?

Yes, unslothai/unsloth currently has 2 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 unslothai/unsloth 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.