Who continues an open-source project?
This catalog researches whether one project succeeds or continues another. A GitHub fork alone does not establish succession. 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-11-15T10:01:58.857Z (UTC).
| Subject (candidate) | Relation | Object (base) | Status | Last verified (UTC) | Current evidence summary |
|---|---|---|---|---|---|
| albumentations-team/albumentationsx successor candidate | successor of? | albumentations-team/albumentations predecessor | observed | 2026-11-08T19:01:41.465Z | Evidence suggests albumentations-team/albumentationsx may succeed albumentations-team/albumentations (directional claim found). Human review required before publication. |
| angular/angular successor candidate | successor of? | angular/angular.js predecessor | observed | 2026-11-14T00:01:37.547Z | 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 | confirmed | 2026-11-14T06:01:44.542Z | 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. |
| biomejs/biome successor candidate | successor of? | rome/tools predecessor | observed | 2026-11-13T16:01:59.956Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| yarnpkg/yarn successor candidate | successor of? | bower/bower predecessor | observed | 2026-11-14T00:01:41.687Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| yshui/picom fork candidate | fork of? | chjj/compton upstream base | confirmed | 2026-11-11T21:02:04.536Z | Evidence suggests yshui/picom is a fork of chjj/compton. Human review required before publication. |
| jertel/elastalert2 successor candidate | successor of? | yelparchive/elastalert predecessor | observed | 2026-11-09T20:01:44.899Z | Evidence suggests jertel/elastalert2 may succeed yelparchive/elastalert (directional claim found). Human review required before publication. |
| element-plus/element-plus successor candidate | successor of? | elemefe/element predecessor | confirmed | 2026-11-14T08:01:19.982Z | Evidence suggests element-plus/element-plus may succeed elemefe/element (directional claim found). Human review required before publication. |
| eza-community/eza successor candidate | successor of? | ogham/exa predecessor | confirmed | 2026-11-11T22:01:30.837Z | Evidence suggests eza-community/eza may succeed ogham/exa (directional claim found). Human review required before publication. |
| ecrc/exageostatcpp successor candidate | successor of? | ecrc/exageostat predecessor | observed | 2026-11-11T06:00:31.361Z | Evidence suggests ecrc/exageostatcpp may succeed ecrc/exageostat (directional claim found). Human review required before publication. |
| fcitx/fcitx5 successor candidate | successor of? | fcitx/fcitx predecessor | observed | 2026-11-13T17:01:00.012Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| python-restx/flask-restx successor candidate | successor of? | noirbizarre/flask-restplus predecessor | observed | 2026-11-11T22:01:32.963Z | Evidence suggests python-restx/flask-restx is a fork of noirbizarre/flask-restplus. Human review required before publication. |
| fossbilling/fossbilling fork candidate | fork of? | boxbilling/boxbilling upstream base | observed | 2026-11-13T18:00:41.467Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| maxpra/gametimenext successor candidate | successor of? | maxpra/gametimex predecessor | observed | 2026-11-12T16:01:41.074Z | Evidence suggests maxpra/gametimenext may succeed maxpra/gametimex (directional claim found). Human review required before publication. |
| godot-rust/gdext successor candidate | successor of? | godot-rust/gdnative predecessor | observed | 2026-11-10T19:01:03.247Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| yaml/go-yaml successor candidate | successor of? | go-yaml/yaml predecessor | observed | 2026-11-11T22:01:34.776Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| stdgraph/graph-v3 successor candidate | successor of? | stdgraph/graph-v2 predecessor | observed | 2026-11-08T19:01:43.691Z | Evidence suggests stdgraph/graph-v3 may succeed stdgraph/graph-v2 (directional claim found). Human review required before publication. |
| theme-next/hexo-theme-next successor candidate | successor of? | iissnan/hexo-theme-next predecessor | observed | 2026-11-12T16:01:44.001Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| golang-jwt/jwt successor candidate | successor of? | dgrijalva/jwt-go predecessor | observed | 2026-11-14T00:01:36.241Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| go-viper/mapstructure fork candidate | fork of? | mitchellh/mapstructure upstream base | confirmed | 2026-11-11T22:01:37.049Z | Evidence suggests go-viper/mapstructure is a fork of mitchellh/mapstructure. Human review required before publication. |
| iamkun/dayjs successor candidate | successor of? | moment/moment predecessor | observed | 2026-11-14T02:00:44.832Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| openvoiceos/ovos-core successor candidate | successor of? | mycroftai/mycroft-core predecessor | observed | 2026-11-14T18:00:59.874Z | Evidence suggests openvoiceos/ovos-core is a fork of mycroftai/mycroft-core. Human review required before publication. |
| mylar3/mylar3 successor candidate | successor of? | evilhero/mylar predecessor | observed | 2026-11-09T20:01:42.969Z | Evidence suggests mylar3/mylar3 may succeed evilhero/mylar (directional claim found). Human review required before publication. |
| sass/dart-sass successor candidate | successor of? | sass/node-sass predecessor | confirmed | 2026-11-14T08:01:20.254Z | 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 | confirmed | 2026-11-14T08:01:20.847Z | Evidence suggests nose-devs/nose2 may succeed nose-devs/nose (directional claim found). Human review required before publication. |
| nvimtools/none-ls.nvim fork candidate | fork of? | jose-elias-alvarez/null-ls.nvim upstream base | observed | 2026-11-11T23:00:10.647Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| jayminwest/warren successor candidate | successor of? | jayminwest/overstory predecessor | observed | 2026-11-11T06:00:33.547Z | Evidence suggests jayminwest/warren may succeed jayminwest/overstory (directional claim found). Human review required before publication. |
| paperless-ngx/paperless-ngx successor candidate | successor of? | jonaswinkler/paperless-ng predecessor | observed | 2026-11-11T19:00:10.401Z | Evidence suggests paperless-ngx/paperless-ngx may succeed jonaswinkler/paperless-ng (directional claim found). Human review required before publication. |
| nuenni/parsec successor candidate | successor of? | nuenni/parsec-plane predecessor | observed | 2026-11-08T15:00:29.897Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| gorf/piecash-community successor candidate | successor of? | sdementen/piecash predecessor | observed | 2026-11-11T06:00:35.530Z | Evidence suggests gorf/piecash-community is a fork of sdementen/piecash. Human review required before publication. |
| postgres/postgres successor candidate | successor of? | mysql/mysql-server predecessor | observed | 2026-11-14T04:00:18.070Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| pulsar-edit/pulsar fork candidate | fork of? | atom/atom upstream base | observed | 2026-11-11T21:01:59.692Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| nhairs/python-json-logger successor candidate | successor of? | madzak/python-json-logger predecessor | confirmed | 2026-11-13T21:00:33.152Z | Evidence suggests nhairs/python-json-logger may succeed madzak/python-json-logger (directional claim found). Human review required before publication. |
| axios/axios successor candidate | successor of? | request/request predecessor | observed | 2026-11-14T08:01:20.183Z | 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-11-14T08:01:20.885Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| searxng/searxng fork candidate | fork of? | searx/searx upstream base | observed | 2026-11-13T21:00:35.071Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| spotbugs/spotbugs successor candidate | successor of? | findbugsproject/findbugs predecessor | observed | 2026-11-10T16:01:02.827Z | Evidence suggests spotbugs/spotbugs may succeed findbugsproject/findbugs (directional claim found). Human review required before publication. |
| go-jose/go-jose successor candidate | successor of? | square/go-jose predecessor | observed | 2026-11-13T23:01:32.837Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| tomboy-notes/tomboy-ng successor candidate | successor of? | tomboy-notes/tomboy predecessor | observed | 2026-11-11T21:02:02.053Z | 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 | confirmed | 2026-11-14T08:01:20.318Z | 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. |
| papermc/velocity successor candidate | successor of? | papermc/waterfall predecessor | observed | 2026-11-14T17:00:41.164Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| vuejs/core successor candidate | successor of? | vuejs/vue predecessor | observed | 2026-11-14T06:01:41.222Z | 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-11-14T06:01:44.744Z | No directional succession or fork claim was found; the current evidence does not establish the researched relationship. |
| yt-dlp/yt-dlp fork candidate | fork of? | blackjack4494/yt-dlc upstream base | confirmed | 2026-11-14T00:01:35.175Z | Evidence suggests yt-dlp/yt-dlp is a fork of blackjack4494/yt-dlc. Human review required before publication. |
| goccy/googlesqlite successor candidate | successor of? | goccy/go-zetasqlite predecessor | observed | 2026-11-08T19:01:46.006Z | Evidence suggests goccy/googlesqlite may succeed goccy/go-zetasqlite (directional claim found). Human review required before publication. |
Feedback
Feedback and research requests are stored privately for operator review. You can ask for help even when the project or relationship is not in our catalog. Submissions never change a verdict or trigger collection by themselves.
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.