Open Divergence Radar Catalog Method Feedback

Is yshui/picom the fork of chjj/compton?

yshui/picom subject · fork candidate fork of? chjj/compton object · upstream base

compton-picom · status confirmed

Data verified at: 2026-09-16T15:45:22.332Z (UTC)

Conclusion status

A human reviewer approved this relationship for the exact current evidence at 2026-09-20T08:22:23.109Z (UTC). The evidence below is the basis of that decision.

Evidence suggests yshui/picom is a fork of chjj/compton. Human review required before publication.

Seed context: 2026-09-16 curated succession candidate; NOT APPROVED. Maintainer documents continuation because original appeared unmaintained; community continuation, not an asserted official transfer. Evidence: https://github.com/yshui/picom/blob/next/History.md

Evidence (1)

Verbatim excerpts from official sources, whitespace-normalized. Full payloads are hashed and retained by the pipeline; collection failures never fabricate evidence.

fork_claim

/branch/next/graph/badge.svg?token=NRSegi0Gze)](https://codecov.io/gh/yshui/picom) https://discord.gg/SY5JJzPgME __picom__ is a compositor for X, and a fork of Compton.
Source
Official source
Revision
f232c180b5…f232c180b5e7cbf91b1944787c4ca7526e6b97e0
First observed
2026-09-16T15:45:33.732Z

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.

EndpointRepoStarsLast pushForkArchived
yshui/picom yshui/picom 4795 2026-06-02T17:39:32Z no no
chjj/compton chjj/compton 2263 2021-06-29T13:48:18Z no no

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.

Version-scoped runtime comparison — literal declarations, not migration advice
yshui/picomchjj/compton

Unknown: no collected package runtime declaration.

Unknown: no collected package runtime declaration.

yshui/picom

Release-pinned deployment declarations

Release commit · v13 · complete

Commit: d87a5ba3af7a9ee3c4e040ee29b2dea7e9e46317

Collection endpoint (may change) · Observed 2026-09-16T22:01:45.164Z

Response SHA-256: 6cb1ce63883970d9b6d33a86244023414f390909c200801a9d841e7f01e501cf

Release tree · v13 · complete

Commit: d87a5ba3af7a9ee3c4e040ee29b2dea7e9e46317

Collection endpoint (may change) · Observed 2026-09-16T22:01:45.164Z

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: 572cb0ec0216a32e195644c90cba8c908513e73547d8e9fcbbf6d40d24400e3f

GitHub release · v13 · not_modified

Official source

GitHub latest published non-prerelease (not a semantic-version ranking). Verified: 2026-09-19T19:00:58.482Z (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-09-16T15:45:27.448Z (UTC)

    Last checked: 2026-09-19T19:00:58.482Z (UTC)

    Source response SHA-256: 1c32011159145443e0189ad0091c4b0dc10b528166ea272fb42868fcd8ed0b6c

    chjj/compton

    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.

    EventEvent timeFirst observedSource
    yshui/picom metadata first observed 2026-09-16T15:45:21.228Z link
    recent commit activity of yshui/picom observed (5 commits in sampled window) 2026-06-02T17:19:38Z 2026-09-16T15:45:22.027Z link
    chjj/compton metadata first observed 2026-09-16T15:45:22.332Z link
    recent commit activity of chjj/compton observed (5 commits in sampled window) 2017-04-30T13:08:49Z 2026-09-16T15:45:22.969Z link
    evidence: fork_claim 2026-09-16T15:45:33.732Z link
    automatic evaluation -> needs_review 2026-09-16T15:45:33.736Z
    human decision: approve 2026-09-20T08:22:23.108Z

    Decision and dispute history

    Review decisions are recorded privately with reasons that stay internal; this public history shows what happened and when, not why.

    KindWhen (UTC)
    automatic evaluation → needs_review2026-09-16T15:45:33.736Z
    human decision: approve2026-09-20T08:22:23.108Z

    To question this report, use the feedback form, select “data error”, and include pair ID compton-picom. Feedback is reviewed privately and does not change a report automatically.

    Snapshot taken at 2026-09-20T12:00:28.104Z (UTC).