alenque-82/supervision
stale
significant_divergence
Selected Prefer this fork only if you need its custom image and API changes and are willing to own divergence. If you want a stable, drop-in supervision library with the latest upstream behavior, upstream is the safer choice.
deeptesh-rout/supervision
stale
significant_divergence
Prefer this fork only if you specifically need its custom annotation/detection changes and are comfortable maintaining a long-lived divergence. If you want a stable, broadly compatible Supervision base, upstream is the better choice.
aryanator/supervision
stale
significant_divergence
Choose the fork only if you need its local fixes or package-layout changes and are prepared to own the maintenance burden. If you want current Supervision capabilities and lower upgrade risk, upstream is the better default.
BiehNandikki/supervision
stale
significant_divergence
Choose upstream unless you specifically need this fork’s custom detection/metrics/tracker behavior and are prepared to maintain a large, stale divergence yourself. For most adopters, upstream is the safer and lower-risk choice.
CodeByPinar/supervision
stale
significant_divergence
Choose this fork only if its local annotator/crop workflow changes are the point. Otherwise, upstream is the better default because this fork is stale, materially behind, and likely missing newer fixes and features.
vmayoral/supervision
stale
significant_divergence
Prefer the upstream project unless you specifically need the fork's custom detection/VLM work or package-layout changes and are prepared to own maintenance. For most adopters, the fork looks too stale and too far behind upstream to be the safer default.
onuralpszr/supervision
active
significant_divergence
Choose this fork if you want the added image/color utilities and are comfortable owning a materially diverged codebase. Choose upstream if compatibility, documentation completeness, and easy upgrades matter more.
lovemonna0305/supervision
stale
significant_divergence
Choose upstream unless you specifically need this branch's customizations and are prepared to own the maintenance burden. This fork looks like a substantial, stale divergence rather than a drop-in improvement, so it favors maintainers of a bespoke variant over new adopters.
Ali-Fayzi/supervision
stale
significant_divergence
Prefer upstream unless you specifically need this fork's older customized behavior. Choose this fork only if you are deliberately staying on a legacy snapshot and can absorb the maintenance burden of a large divergence.
ashishpatel26/supervision
stale
significant_divergence
Choose upstream unless you specifically need this fork's older, customized behavior. This fork is materially behind and looks better as a legacy/private variant than as a starting point for new work.