SQLite is open-source, meaning that you can make as many copies of it as you want and do whatever you want with those copies, without limitation. But SQLite is not open-contribution. In order to keep SQLite in the public domain and ensure that the code does not become contaminated with proprietary or licensed content, the project does not accept patches from unknown persons.
In other words, the reasoning is that since the code is released to the public domain, they want to ensure they can continue doing so without encumbering or confusing future releases with tainted contributions. Quite admirable.
So even if those 3 developers disappear tomorrow, you can fork the source code and compile and maintain your own.
https://www.sqlite.org/src/doc/trunk/README.md
And it's already been sustained for 20 years meaning it has outlasted the great majority of software projects out there.
This isn’t even a particularly strange arrangement for open source. See The Cathedral and the Bazaar.
Until I read the transcript, just now, I had confused SQLite's origins (a General Dynamics contract with the US Navy) with its through-2050 support contract, which, it turns out, is with Airbus.
Either way, that doesn't make it "closed source" like you said in the other comment.
Anyone on the planet can make changes to it and distribute those changes. The only thing those 3 can do that the rest of us cannot is get their changes into the copies distributed at sqlite.org.
First off, even though the source code is public domain, you can't contribute since it is closed source: https://sqlite.org/copyright.html
There are 3 developers who maintain the project https://www.sqlite.org/crew.html and operate under a "code of ethics" that used to be called their "code of conduct" https://sqlite.org/codeofconduct.html
While it succeeded in getting widely adopted I have trouble believing that this is sustainable.