Discofork
Repository brief

go-gorm/gorm

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T09:50:05.454Z
1mo ago

go-gorm/gorm

GORM is a mature Go ORM focused on developer-friendly database access. It has a large user base and ecosystem footprint, with 39,632 stars and 4,144 forks, an active default branch (`master`), and recent commits through 2026-03-23.

GitHub
Loading tags...
Stars39,632
Forks4,144
Default branchmaster
Last pushed2026-03-23T10:05:06Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if you must stay on GORM v1. For new work or for teams that want active upstream progress, upstream GORM is the better default.

Choose this fork only if you need its local ORM behavior and are prepared to maintain it yourself. If you want current GORM fixes, broader compatibility, or active upstream support, upstream is the safer default.

Prefer upstream unless you specifically need this fork’s older context-oriented changes and are willing to maintain a significantly diverged codebase yourself.

Choose this fork only if Cassandra support is the primary requirement and you are comfortable living on an old, highly divergent codebase. For general GORM adoption, upstream is the better fit because it is far more current, broader in scope, and actively maintained.

Prefer upstream unless you need a pinned historical snapshot; this fork adds no visible capabilities and is substantially behind current GORM.

Choose this fork only for legacy compatibility with ngorm-specific code. For new work, upstream GORM is the better default because it is actively maintained and far more complete.

Choose this fork only if you specifically need its older dialect/Oracle-oriented changes or are maintaining an existing dependency on this branch. For general GORM adoption, upstream is far safer because this fork is stale and materially behind.

Prefer this fork only if you specifically want its custom query SQL construction and cache-oriented examples. For general GORM use, upstream is the safer choice because this fork is stale and materially behind.

Choose upstream GORM unless you are already tied to this fork’s older refactor. This fork looks like a legacy, significantly diverged codebase with limited maintenance, so it is mainly attractive for legacy compatibility or niche API preferences rather than new adoption.

Prefer upstream unless you specifically need this exact frozen snapshot; this fork adds no visible capabilities and is materially behind current GORM.

go-gorm/gorm · Discofork