Is fcitx/fcitx5 the successor of fcitx/fcitx?
fcitx5-fcitx4-successor · status observed
Data verified at: 2026-11-13T17:01:00.012Z (UTC)
Conclusion status
No confirmed conclusion exists for this pair. The evidence below is presented for
transparency; a relationship conclusion requires a human review that has not happened,
or a previous decision no longer matches the current evidence.
No directional succession or fork claim was found; the current evidence does not establish the researched relationship.
Seed context: Researched 2026-10-09; NOT APPROVED; pending the normal scheduled collection/evaluation and human review. The predecessor README identifies Fcitx 4 as maintenance-only, asks users not to open new issues or pull requests there, and points them to Fcitx 5. The Fcitx 5 repository describes itself as the next generation of fcitx. Distinct GitHub repository IDs: Fcitx 5 40201953, Fcitx 4 4401745. Fcitx 4 is archived; Fcitx 5 is not archived and was pushed 2026-10-09T14:18:07Z. This records project succession only; it makes no feature-compatibility claim. Sources: https://github.com/fcitx/fcitx/blob/master/README and https://github.com/fcitx/fcitx5/blob/master/README.md.
Observed repository facts
As of the last verified collection. These are facts about the snapshots, not
activity verdicts — a low number is not a claim that a project is inactive.
Versions & deployment facts
Official release and package declarations, compared independently of the relationship verdict.
These are not installation tests or a migration guarantee. Missing declarations mean unknown.
fcitx/fcitx5
Release-pinned deployment declarations
Release commit · 5.1.12 · complete
Commit: 7d71627695b49c06a4270f4d8106e84afb75cddb
Collection endpoint (may change) · Observed 2026-10-09T15:00:29.903Z
Observation is outside the freshness window. Immutable evidence is retained; current registry availability is unknown.
Response SHA-256: b1b7a4ee45ba59739ddd63aa649e2bf9ff34940d365c2a86b046a3dbd4639896
Release tree · 5.1.12 · complete
Commit: 7d71627695b49c06a4270f4d8106e84afb75cddb
Collection endpoint (may change) · Observed 2026-10-09T15:00:29.903Z
Observation is outside the freshness window. Immutable evidence is retained; current registry availability is unknown.
File search coverage: selected_manifest_names. Only selected manifest filenames were searched; fixtures and vendored dependency directories are excluded. Unlisted declarations remain unknown.
Response SHA-256: 03bcb9e909c63d5e22ea1e2578ef2c539ddf8c3395347fe3fc901c3a6992201d
GitHub release · 5.1.12 · not_modified
Official source
GitHub latest published non-prerelease (not a semantic-version ranking). Verified: 2026-11-14T11:00:39.839Z (UTC).
Listed release assets only. Asset names do not prove platform support or successful execution.
- Runtime declarations
Not declared / unknown
- Operating systems
Not declared / unknown
- CPU architectures
Not declared / unknown
- C libraries
Not declared / unknown
Direct dependency declarations
Not declared / unknown
Published artifacts (0)
Provenance
Parser: software-1
First observed: 2026-10-09T15:00:29.903Z (UTC)
Last checked: 2026-11-14T11:00:39.839Z (UTC)
Source response SHA-256: 860503c6bf6a7fccbc9aff177a8aa77c84083c47647078fb5092c79e81b1c4c4
fcitx/fcitx
Release-pinned deployment declarations
Unknown: no release-pinned files have been collected. The default branch is not substituted.
GitHub release · Unknown version · stale evidence
Latest collection: unavailable. No verified release declaration is available. This does not mean the project has no releases or platform support.
Official source
Timeline
“Event time” is an upstream timestamp when the source provides one; “first observed” is when
this project saw it. They are deliberately separate columns.
Decision and dispute history
Review decisions are recorded privately with reasons that stay internal; this
public history shows what happened and when, not why.
To question this report, use the feedback form,
select “data error”, and include pair ID fcitx5-fcitx4-successor.
Feedback is reviewed privately and does not change a report automatically.
Snapshot taken at 2026-11-15T10:01:58.857Z (UTC).