Open-source succession, fork, and continuation research
This catalog tracks research questions of the form “did project A continue as, fork into, or get replaced by project B?”. Every relationship claim carries its verbatim evidence and a review status. Nothing is confirmed without a recorded human decision, and collection gaps never masquerade as project inactivity.
Search reports
Loading search index…
Pair catalog
Status values: confirmed (human-reviewed against current evidence), disputed (open challenge blocks confirmation), observed (evidence recorded, no confirmed conclusion). Data verified at: 2026-09-16T12:00:57.982Z (UTC).
| Subject (candidate) | Relation | Object (base) | Status | Last verified (UTC) | Current evidence summary |
|---|---|---|---|---|---|
| angular/angular successor candidate | successor of? | angular/angular.js predecessor | observed | 2026-09-11T16:50:22Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| babel/babel successor candidate | successor of? | babel/babel-eslint predecessor | observed | 2026-09-11T16:53:02Z | Evidence suggests babel/babel may succeed babel/babel-eslint (directional claim found). Human review required before publication. Supporting: a registry marks the predecessor package deprecated. |
| yarnpkg/yarn successor candidate | successor of? | bower/bower predecessor | observed | 2026-09-11T16:50:39Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| element-plus/element-plus successor candidate | successor of? | elemefe/element predecessor | observed | 2026-09-11T16:53:08Z | Evidence suggests element-plus/element-plus may succeed elemefe/element (directional claim found). Human review required before publication. |
| tursodatabase/libsql fork candidate | fork of? | sqlite/sqlite upstream base | observed | 2026-09-11T16:50:54Z | Evidence suggests tursodatabase/libsql is a fork of sqlite/sqlite. Human review required before publication. |
| mariadb/server fork candidate | fork of? | mysql/mysql-server upstream base | observed | 2026-09-11T16:51:02Z | Evidence suggests mariadb/server is a fork of mysql/mysql-server. Human review required before publication. |
| moby/moby fork candidate | fork of? | docker/docker upstream base | observed | 2026-09-11T16:51:11Z | Repository identity changed: a recorded locator now resolves to a different GitHub id. Human review required. |
| iamkun/dayjs successor candidate | successor of? | moment/moment predecessor | observed | 2026-09-11T16:51:20Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| sass/dart-sass successor candidate | successor of? | sass/node-sass predecessor | observed | 2026-09-11T16:53:16Z | Evidence suggests sass/dart-sass may succeed sass/node-sass (directional claim found). Human review required before publication. Supporting: a registry marks the predecessor package deprecated. |
| nose-devs/nose2 successor candidate | successor of? | nose-devs/nose predecessor | observed | 2026-09-11T16:53:20Z | Evidence suggests nose-devs/nose2 may succeed nose-devs/nose (directional claim found). Human review required before publication. |
| opentofu/opentofu fork candidate | fork of? | hashicorp/terraform upstream base | observed | 2026-09-11T16:51:44Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| postgres/postgres successor candidate | successor of? | mysql/mysql-server predecessor | observed | 2026-09-11T16:51:48Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| legrandin/pycryptodome fork candidate | fork of? | pycrypto/pycrypto upstream base | observed | 2026-09-11T16:53:23Z | Evidence suggests legrandin/pycryptodome is a fork of pycrypto/pycrypto. Human review required before publication. |
| valkey-io/valkey fork candidate | fork of? | redis/redis upstream base | observed | 2026-09-11T16:52:04Z | Evidence suggests valkey-io/valkey is a fork of redis/redis. Human review required before publication. |
| axios/axios successor candidate | successor of? | request/request predecessor | observed | 2026-09-11T16:53:13Z | Supporting: a registry marks the predecessor package deprecated. Supporting: the predecessor's README declares the project deprecated. |
| encode/httpx successor candidate | successor of? | psf/requests predecessor | observed | 2026-09-11T16:53:24Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| eslint/eslint successor candidate | successor of? | palantir/tslint predecessor | observed | 2026-09-11T16:53:17Z | Evidence suggests eslint/eslint may succeed palantir/tslint (directional claim found). Human review required before publication. Supporting: a registry marks the predecessor package deprecated. Supporting: the predecessor's README declares the project deprecated. |
| vuejs/core successor candidate | successor of? | vuejs/vue predecessor | observed | 2026-09-11T16:52:37Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| vuejs/create-vue successor candidate | successor of? | vuejs/vue-cli predecessor | observed | 2026-09-11T16:53:04Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| zlib-ng/zlib-ng fork candidate | fork of? | madler/zlib upstream base | observed | 2026-09-11T16:52:53Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
Feedback
Feedback is private and reviewed by the operator. Public submissions are held in a cloud inbox until imported into the private review database, then removed from the inbox. Feedback never changes a verdict or triggers collection by itself.
Why statuses differ per pair
A pair is only presented as confirmed when a human decision exists for the exact current evidence, no dispute is open, the two endpoints have distinct repository identities, and every necessary data source was collected successfully within the freshness window. Anything else stays observed — that includes projects with plenty of stars and commits but no directional claims. See the method page for the full policy.