Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI researchers, computer vision engineers, image / photo-editing app developers, mobile / edge ML engineers, AI-curious readers, and any developer building image inpainting pipelines where model size and inference latency matter -- and who can pair hustvl/Moebius with the ECCV'26 paper (arXiv 2606.19195) for the research surface, Hugging Face for the model distribution surface, the Moeb
Who should use it
Who should skip it
Skip hustvl/Moebius if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
hustvl/Moebius is tracked by RepoRadar as a 0.2b-parameter image inpainting in the 0.2B Image Inpainting Framework (10B-Level Perfo section. It was first seen on 2026-07-07 and last updated on 2026-07-07. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for hustvl/Moebius are workflow potential (9.3) and novelty (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned hustvl/Moebius a composite score of 8.2 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The 475* / 39-fork repo is at active maintenance but the 0.2B-vs-10B claim is benchmark-dependent -- treat the first evaluation cycle as a smoke test (read the ECCV'26 paper + install dependencies + download pre-trained weights + run a smoke-test inpainting on a natural-scene image and a portrait-scene image + compare against FLUX.1-Fill-Dev on a representative workload) before relying on the framework in production; the 15x inference speedup depends on the hardware -- the consumer SHOULD benchmark against a representative 10B-level baseline on the deployment hardware before adopting in production; the edge / mobile deployment depends on quantization + inference framework (PyTorch / ONNX / TensorRT) -- the consumer SHOULD benchmark the deployment surface before adopting in a mobile / edge workflow; the 6-benchmark evaluation may not cover every inpainting domain -- the consumer SHOULD benchmark against a representative inpainting workload before deploying to a production image pipeline.