FAQ
Common questions, answered without hedging.
Does ForkReason tell me if a repository was stolen?
No. ForkReason reports development lineage: whether one repository appears to derive from another, share an upstream, or have no detectable relationship. Those are not legal conclusions and ForkReason does not make them.
Why does it often say INSUFFICIENT_EVIDENCE?
Because most similar-looking repository pairs are not related, and a large fraction of real relationships do not leave enough trace to distinguish from coincidence. Returning a verdict in those cases would make the tool worse, not better.
Do I need a wallet?
Only to record a finding on chain or submit a challenge. Analysis and every read are free and walletless.
Is my repository data sent anywhere?
Snapshots are written to disk on the ForkReason server for analysis. Only a bounded evidence digest goes to a model for the decision, and never a whole repository. Nothing is sent to a third party beyond the GenLayer network if you choose to record a result.
Can a malicious repository manipulate the verdict?
It can try. That is why adversarial fixtures are part of the release gate, and why validators independently re-derive the decision instead of trusting the leader.
How long does an analysis take?
It depends on repository size, and ForkReason does not pretend to predict it. The progress view shows which stage is running and how long it has actually been running.