I've managed to replicate the issue!
```
(github-to-sqlite) /tmp % sqlite-utils tables --counts github.db | grep licenses
{"table": "licenses", "count": 7},
{"table": "licenses_fts_data", "count": 35},
{"table": "licenses_fts_idx", "count": 16},
{"table": "licenses_fts_docsize", "count": 9151},
{"table": "licenses_fts_config", "count": 1},
{"table": "licenses_fts", "count": 7},
(github-to-sqlite) /tmp % github-to-sqlite repos github.db dogsheep
(github-to-sqlite) /tmp % sqlite-utils tables --counts github.db | grep licenses
{"table": "licenses", "count": 7},
{"table": "licenses_fts_data", "count": 45},
{"table": "licenses_fts_idx", "count": 26},
{"table": "licenses_fts_docsize", "count": 9161},
{"table": "licenses_fts_config", "count": 1},
{"table": "licenses_fts", "count": 7},
```
Note how the number of rows in `licenses_fts_docsize` goes from 9151 to 9161.
I dug into this and it turns out that `github-to-sqlite repos` command does indeed run the following SQL 10 times:
```
INSERT OR REPLACE INTO [licenses] ([key], [name], [node_id], [spdx_id], [url]) VALUES
(?, ?, ?, ?, ?);
```
So I like your `PRAGMA recursive_triggers` theory. I'm going to give that a try.