← All database systems
YugabyteDB is supported by SQLancer — the main repository ships a
testing implementation for it.
SQLancer is credited with 54 bugs in it, reported between 2021-09-29 and
2026-07-17.
Its source is at yugabyte/yugabyte-db.
A further 6 reports were
filed and rejected by the developers as invalid or duplicate. Those are kept
in the dataset for transparency and are excluded from every count here.
How the project uses SQLancer
Official testing
The YugabyteDB project maintains its own SQLancer fork, 149 commit(s) ahead of upstream, last updated 2026-09-12.
yugabyte/sqlancer is a fork of sqlancer/sqlancer under the YugabyteDB project's own GitHub organisation, 149 commit(s) ahead of upstream./github.com/yugabyte/sqlancer
last verified 2026-09-13
How the bugs break down
By year reported
- 2021
-
3
- 2022
-
16
- 2023
-
3
- 2024
-
1
- 2025
-
26
- 2026
-
3
- Year not recorded
-
2
Who found them
- Found by the SQLancer project
-
13
- Found by someone outside the project
-
39
- Reporter not recorded
-
2
By status
- Fixed
-
24
- Open
-
30
By symptom
- Unclassified
-
54
By technique
- Technique not recorded
-
54
Why each bug counts
- The reproducer carries SQLancer's generated schema
-
41
- The report names SQLancer
-
9
- Filed by someone who runs SQLancer campaigns
-
2
- Listed in the project's own bug repository
-
2
Who reported them (5)
- qvad
-
35
- bajinsheng
-
13
- def-
-
2
- rojasbinny-yb
-
1
- yugabyte-ci
-
1
Every bug on record (60)
One row per report, newest first, each linking to the report itself. Rejected
reports are marked and are not part of any count above.
Every figure on this page is computed from
_data/impact/.
The attribution policy
explains what has to be true for a bug to be counted.