Discofork
Repository brief

sequelize/sequelize

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:33.529Z
1mo ago

sequelize/sequelize

Sequelize is a large, active open-source ORM for modern Node.js and TypeScript. It targets PostgreSQL, MySQL, MariaDB, SQLite, MS SQL Server, Snowflake, Oracle DB, DB2, and DB2 for IBM i, and the repo is still maintained with recent commits and a large contributor/community footprint.

GitHub
Loading tags...
Stars30,351
Forks4,333
Default branchmain
Last pushed2026-03-23T04:59:53Z
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 Oracle support is the deciding requirement and you can absorb the maintenance risk. If you need current Sequelize behavior, broader dialect coverage, or active upstream updates, upstream is the safer choice.

Prefer this fork only if you are maintaining an existing IBMDB-centered stack and need its older, DB2-oriented workflow surface. For new work, or if you want current Sequelize fixes and tooling, upstream is the safer choice.

Prefer this fork only if you are maintaining an old Sequelize-based system and need its specific legacy patches. For new work, active upstream Sequelize is the safer choice.

Prefer this fork only if Snowflake support is the primary requirement and you are comfortable living on an old, divergent codebase. If you want an actively maintained ORM with current fixes across many databases, upstream is the safer choice.

Prefer this fork only if Oracle support in this specific legacy branch is the main requirement. For most adopters, upstream is the better choice because it is far more current, actively maintained, and already includes broader modern dialect and tooling support.

Choose this fork if DM8 support is the primary requirement. Prefer upstream Sequelize if you need the broadest current feature set, newer releases, or easier long-term maintenance.

Choose this fork only if you need an old, customized Sequelize branch for legacy compatibility. For new work or active maintenance, upstream is the far better fit.

Prefer this fork only if you need its legacy Sequelize behavior or its specific dialect/type fixes. For most new or actively maintained projects, upstream Sequelize is the safer choice because this fork is stale and materially behind.

Prefer this fork only if you need a frozen, legacy Sequelize baseline. For new work or active maintenance, upstream is the better choice.

Prefer upstream unless you specifically need this older snapshot and are prepared to own maintenance yourself; the fork’s value is legacy stability, not currency or breadth.

sequelize/sequelize · Discofork