Is tursodatabase/libsql the fork of sqlite/sqlite?

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 tursodatabase/libsql is a fork of sqlite/sqlite. Human review required before publication.

Seed context: Research question: is libSQL a fork of SQLite? SQLite's canonical VCS is Fossil; the GitHub repo is a mirror.

Evidence (3)

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

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.

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 libsql-sqlite. Feedback is reviewed privately and does not change a report automatically.