db-to-sqlite VS healthkit-to-sqlite

I was surprised to see SQLite listed as a source but not as a destination. Any big reasons for that or is it just something you haven't got around to implementing yet?

I've been getting a huge amount of useful work done over the past few years sucking data from other systems into SQLite files on my own computer - I even have my own small db-to-sqlite tool for this (built on top of SQLAlchemy) - https://github.com/simonw/db-to-sqlite

> Technically I’m actively maintaining all of them, in that if someone reports a bug I’ll push out a fix.

Ironically, I toned down my enthusiasm for this author's (many) projects after my initial perusing led me to something interesting[0] that didn't work, and the subsequent issues and minor (but linked to issues!) PRs I contributed went completely without response for the last few years. They're still open.

To be clear, I'm grateful for the work the author is freely providing for me and the world! And I could certainly do a better job with some of the projects I help maintain as well. He's under no obligation to respond to issues if he doesn't have time or just doesn't want to. But it does speak to how difficult it can be to maintain over a hundred projects, even if you have a system.

[0]: https://github.com/dogsheep/healthkit-to-sqlite

I've been using the sqlite_utils Python library to build a whole suite of tools for importing data from various different sources into SQLite, including healthkit-to-sqlite, swarm-to-sqlite, twitter-to-sqlite, inaturalist-to-sqlite, google-takeout-to-sqlite, github-to-sqlite, genome-to-sqlite, pocket-to-sqlite, hacker-news-to-sqlite, evernote-to-sqlite.