Grounded in records
Relationships come from Git objects, manifests and documents. Open the records behind a connection to see how it was found.
LAYERS
Paste a GitHub repository. GitLineage traces its ancestry, dependencies and declared attribution — and shows the evidence behind every relationship it draws.
01 · Identify
Repository identity
02 · Collect
Verifiable records
03 · Connect
Typed connections
04 · Verify
Supported ancestry
Analysis follows the source records; open any connection to inspect its evidence.
Repository address
/owner/repository
Cargo.tomlA manifest records composition.
It does not establish ancestry.
Relationships come from Git objects, manifests and documents. Open the records behind a connection to see how it was found.
Inspect the source, status and supporting evidence. Declared, verified and detected records remain clearly distinguished.
Dependencies and references are separate from ancestry. Similarity is a lead to investigate, never proof of derivation.
Repository analysis
Evidence first. Git objects, manifests and declarations are checked before relationships enter your graph. Dependencies and references do not prove ancestry.
Your explorer is next. When analysis finishes, follow relationships, inspect their evidence, or open the repository’s Git history.
Select a node or relationship in Graph or Relations to read its actual evidence.