This looks like an upstream bug. There's only one `go.mod` file in the original repo, and because glebarez imports modernc.org/sqlite and modernc.sqlite is also one of the drivers tested, glebarez tests will use the modernc.org/sqlite version mentioned in the go.mod file of the benchmark repository, not the one specified [here](https://github.com/glebarez/go-sqlite/blob/master/go.mod). Caught when optimizing modernc.org/sqlite and the numbers for glebarez improved unexpectedly as well. That *should* happen once glebarez updates its go.mod file, but now it reveals unintended side effects of having all the test command in a single module. Solution: Isolate commands dependencies in the `vendor` subdir by making all of them a standalone module, or submodule, if you prefer. The `go.mod` files in these submodule should be exactly the same as found at the vendor source repo for the particular tested tag. **Note**: This also means the results already published at @v0.1.0 should not be considered valid.