Dependency-Track vs Cursor

Dependency-Track is deep in a 5.0.0 release candidate series, cutting rc.2 through rc.5 within a single week. A large share of every release is the v4-migrator: BIGINT casts during extract, ANALYZE on staging tables before transform, component dedup before joining repo metadata, cross-schema type dependencies, trigger deactivation, permission table bootstrap. Nearly every commit in the window is authored by a single maintainer.

This is a major version defined by what it removes and how safely it moves people across. rc.2 dropped the compatibility shim translating v4-era alpine.* and unprefixed property names to dt.* equivalents, and made the API server refuse to start on a legacy key rather than silently misconfigure. Around that migration work, the policy engine keeps gaining inputs — component hash mismatch conditions, latest version publish timestamps exposed to CEL — and latest-version detection is being tuned per ecosystem so Maven reports stable releases rather than prereleases.

Expect further release candidates focused on migrator robustness before 5.0.0 goes stable, since four of them in one week were still finding extract and transform bugs in the same code path.