Open Divergence Radar Catalog Method Feedback

Is valkey-io/valkey the fork of redis/redis?

valkey-io/valkey subject · fork candidate fork of? redis/redis object · upstream base

redis-valkey · status observed

Data verified at: 2026-09-11T16:52:04Z (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.

Evidence suggests valkey-io/valkey is a fork of redis/redis. Human review required before publication.

Seed context: Research question: is valkey an active fork of redis? GitHub fork-network metadata is the candidate signal; not a confirmed fact.

Evidence (1)

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

KindExcerptSourceRevisionFirst observed
fork_claim
JAYC5F)](https://codecov.io/gh/valkey-io/valkey) https://securityscorecards.dev/viewer/?uri=github.com/valkey-io/valkey This project was forked from the open source Redis project right before the transition to their new source available licenses.
source
5c2b47b456…5c2b47b4568ba8660f4c1a51a980251adc9f9651
2026-09-12T02:59:28Z

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
valkey-io/valkey valkey-io/valkey 27174 2026-09-11T16:11:07Z no no
redis/redis redis/redis 76325 2026-09-10T12:12:23Z 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.

valkey-io/valkey

GitHub release · 9.1.2

Official source

GitHub latest published non-prerelease (not a semantic-version ranking). Verified: 2026-09-16T11:13:53.818Z (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-16T11:13:53.818Z (UTC)

    Last checked: 2026-09-16T11:13:53.818Z (UTC)

    Source response SHA-256: d68ebf69d6b066a29b4b250bbf5f0957193dc30f8351d5327690b0d4f3ce958e

    redis/redis

    GitHub release · 8.10.1

    Official source

    GitHub latest published non-prerelease (not a semantic-version ranking). Verified: 2026-09-16T11:13:53.818Z (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 (1)
    Provenance

    Parser: software-1

    First observed: 2026-09-16T11:13:53.818Z (UTC)

    Last checked: 2026-09-16T11:13:53.818Z (UTC)

    Source response SHA-256: 3fc6edd2ee3804f3da538c30cf778257cb3ca8a2c972f6a0189989947d7ee8b1

    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
    valkey-io/valkey metadata first observed 2026-09-11T16:25:05Z link
    recent commit activity of valkey-io/valkey observed (5 commits in sampled window) 2026-09-11T16:11:07Z 2026-09-11T16:25:08Z link
    redis/redis metadata first observed 2026-09-11T16:25:09Z link
    recent commit activity of redis/redis observed (5 commits in sampled window) 2026-09-10T12:12:23Z 2026-09-11T16:25:12Z link
    automatic evaluation -> insufficient_data 2026-09-11T16:26:28Z
    automatic evaluation -> needs_review 2026-09-11T16:29:17Z
    evidence: fork_claim 2026-09-11T16:29:17Z link
    automatic evaluation -> needs_review 2026-09-11T16:53:25Z
    evidence: fork_claim 2026-09-11T16:53:25Z link
    automatic evaluation -> needs_review 2026-09-11T16:58:19Z
    evidence: fork_claim 2026-09-11T16:58:19Z link
    automatic evaluation -> needs_review 2026-09-12T02:55:35Z
    evidence: fork_claim 2026-09-12T02:55:35Z link
    automatic evaluation -> needs_review 2026-09-12T02:57:05Z
    evidence: fork_claim 2026-09-12T02:57:05Z link
    automatic evaluation -> needs_review 2026-09-12T02:59:28Z
    evidence: fork_claim 2026-09-12T02:59:28Z link

    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 → insufficient_data2026-09-11T16:26:28Z
    automatic evaluation → needs_review2026-09-11T16:29:17Z
    automatic evaluation → needs_review2026-09-11T16:53:25Z
    automatic evaluation → needs_review2026-09-11T16:58:19Z
    automatic evaluation → needs_review2026-09-12T02:55:35Z
    automatic evaluation → needs_review2026-09-12T02:57:05Z
    automatic evaluation → needs_review2026-09-12T02:59:28Z

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

    Snapshot taken at 2026-09-16T13:11:39.533Z (UTC).