chongruo/detectron2-ResNeSt
slowing
significant_divergence
Selected Choose this fork if ResNeSt support is the priority. Avoid it if you want the newest Detectron2 behavior, broader backbone options, or low-maintenance upstream compatibility.
airsplay/py-bottom-up-attention
stale
significant_divergence
Choose this fork if bottom-up attention and its surrounding experiment stack matter more than staying current with upstream Detectron2. Avoid it if you want an actively maintained, general-purpose Detectron2 base.
hpanwar08/detectron2
stale
significant_divergence
Choose this fork if you need a document-layout-oriented Detectron2 variant and can tolerate major divergence and low maintenance. Choose upstream if you want current Detectron2 features, cleaner deployment/export paths, and easier long-term upkeep.
ivanpp/detectron2
stale
significant_divergence
Prefer this fork if Windows support is the main requirement and you can tolerate being behind upstream. Prefer upstream if you need current model support, active maintenance, or the broadest Detectron2 feature set.
DGMaxime/detectron2-windows
stale
significant_divergence
Choose this fork if Windows support is the main requirement and you can accept an old, heavily diverged codebase. Choose upstream if you want current Detectron2 features, active maintenance, and less upgrade risk.
youngwanLEE/detectron2
stale
significant_divergence
Choose this fork only if you specifically need the VoVNet-oriented research setup or its historical behavior. For general Detectron2 work, upstream is the better default because this fork is old and heavily diverged.
MaureenZOU/detectron2-xyz
stale
significant_divergence
Prefer upstream unless you specifically need this fork's training-loop and dataloader behavior. This fork looks stale and materially stripped down, so it is better as a legacy or specialized variant than as a general-purpose Detectron2 base.
Choose this fork if your priority is build, packaging, or CI convenience in a constrained environment. Choose upstream if you want the latest Detectron2 fixes, broader maintenance, and less merge debt.
Prefer this fork only if you need its specific project-level tweaks and can tolerate an old upstream base. If you want current Detectron2 fixes, deployment polish, and broader maintenance, upstream is the better choice.
neurolaboratories/detectron2
stale
significant_divergence
Prefer this fork only if its DensePose and Windows-specific changes match an existing dependency. For most adopters, upstream Detectron2 is the better choice because this fork is stale, heavily diverged, and likely missing modern features and maintenance.