"SQLite Studio" seems like a poor choice of name given that it's already in use[0].
See this Github post where SQLite author asserts his trademark https://github.com/vapor/sqlite-kit/issues/47 on another project that uses SQLite in the name.
Both projects should change their names.
While SQLite is open source, the trademark is retained by the authors https://sqlite.org/consortium_agreement-20071201.html
If this were not the case and a trademark is USA specific, how is is to be assessed if, as in the case of SQLite Database Explorer, someone from Ethiopia or, as in the case of SQLiteStudio, someone from Poland violates it? Or the other way round, if someone from the USA violates an Ethiopian or Polish trademark?
At the time we were taught about the Madrid Protocol (US implementation https://www.uspto.gov/ip-policy/international-protection/mad...), which gives you some time to register it in each country after the first registration. If you register it within this alloted time, you retain priority over other people who want to register it too.
You do have to register it, but more importantly, enforce it, yourself worldwide.
IP Lawfirms usually provide this as a service.
On the practical matter of "Is the trademark registered internationally?". Have to do a search in each country's trade mark office. It's very tedious (not every mark is in text, some are pictures, sounds).
From the linked GitHub issue:
> Please do NOT use the name "SQLite" for your project.
Resolution PR: https://github.com/vapor/sqlite-kit/pull/52/files
He may want to be nice, or have done a deal or any number of reasons. That doesn't mean he can't stop them from using it altogether.
Also he can change his mind down the track.
Whether it is infringing or not is up to many factors in each case, but simply extending it is not going to protect you in every case.
If we want a definitive answer, would have to take this to a court.
Source: studied IP in Law school, but not a professor or anything.
"You are welcomed to use "SQLite" as part of the name for your software, so that people know that it uses SQLite. For example, you might call your software "SQLite Wrapper for Swift" or "Vapor's Swift SQLite Wrapper". But you may not use the unqualified name "SQLite"."