- Passed security review or already Wikimedia deployed
- Voting CI structure tests
- Runs MediaWiki-CodeSniffer
- Runs phan
- Supports MySQL, SQLite, and Postgres (sqlite doesn't support regex, so that option is hidden)
- GPL v2 or later compatible license
- Extension's default configuration provides optimal experience
- Tested with web installer
Oh, I just looked at this set of tasks now, and unfortunately, it turns out that Replace Text doesn't support SQLite - someone just sent me an email about that a few days ago, by coincidence. I don't know if it can- according to the guy, you can't use REGEXP and REPLACE (or SQLite's equivalents of those) together in the same query within SQLite. I don't know if that's a deal breaker if true.
Conversely, though, Replace Text does use the GPLv2.
For SQLite, I found https://stackoverflow.com/questions/4663368/custom-regexp-function-to-be-used-in-a-sqlite-select-statement that is promosing.
I have no idea if sqlite support is a requirement for being bundled.
Bundled extensions should generally be compatible with most setups, and mysql/sqlite/postgres seems like a reasonable baseline. I think most problematically, the installer doesn't have any way right now to hide extensions if they don't support the database engine that was picked.
I just checked in to Replace Text a change so that the "use regex" checkbox doesn't appear if the database is SQLite. So now Replace Text works fine with SQLite, just with more limited functionality. (Regex querying was the only thing that SQLite couldn't handle, apparently.) Is that good enough?