Materialize and SQLancer

Materialize is supported by SQLancer — the main repository ships a testing implementation for it. No bugs in it are attributed to SQLancer.

How the project uses SQLancer

Official testing

The Materialize project maintains its own SQLancer fork, 28 commit(s) ahead of upstream, last updated 2026-07-24.

RUN git clone https://github.com/MaterializeInc/sqlancer \
test/sqlancer/Dockerfile in the Materialize repository invokes SQLancer.
test/sqlancer/Dockerfile last verified 2026-09-13

from materialize.sqlancer import create_services, run_sqlancer
test/sqlancer/mzcompose.py in the Materialize repository invokes SQLancer.
test/sqlancer/mzcompose.py last verified 2026-09-13

name: sqlancer
test/sqlancer/mzbuild.yml in the Materialize repository is part of a SQLancer setup the project maintains.
test/sqlancer/mzbuild.yml last verified 2026-09-13

RUN git clone --single-branch --depth=1 https://github.com/MaterializeInc/sqlancerplusplus \
test/sqlancerplusplus/Dockerfile in the Materialize repository invokes SQLancer.
test/sqlancerplusplus/Dockerfile last verified 2026-09-13

from materialize.sqlancer import create_services, run_sqlancer
test/sqlancerplusplus/mzcompose.py in the Materialize repository invokes SQLancer.
test/sqlancerplusplus/mzcompose.py last verified 2026-09-13

MaterializeInc/sqlancer is a fork of sqlancer/sqlancer under the Materialize project's own GitHub organisation, 28 commit(s) ahead of upstream.
/github.com/MaterializeInc/sqlancer last verified 2026-09-13

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.