head to head · open source
typeorm vs JSqlParser
typeorm has 36,661 GitHub stars, 6,691 forks, 646 open issues and last shipped 7 days ago. JSqlParser has 5,970 stars, 1,446 forks, 12 open issues and last shipped 5 days ago. typeorm leads on adoption by 514% (36,661 vs 5,970 stars). typeorm is written in TypeScript under MIT; JSqlParser is written in Java under Apache-2.0. typeorm has attracted 18% as many forks as stars, JSqlParser 24%. JSqlParser was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 3 topic tags (mysql, postgresql, sqlserver), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| typeorm | JSqlParser | |
|---|---|---|
| GitHub stars | ★ 37K | ★ 6.0K |
| License | MIT | Apache-2.0 |
| Written in | TypeScript | Java |
| Last push | 2026-10-29 | 2026-10-31 |
| Forks | ⑂ 6.7K | ⑂ 1.4K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick typeorm if
- You weight community size — 37K stars and counting
- You want the MIT license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick JSqlParser if
- You want the JSqlParser feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Java
- You evaluated both and JSqlParser fits your workflow better
About typeorm
TypeORM is an ORM that can run in Node.js, Browser, Cordova, Ionic, React Native, NativeScript, Expo, and Electron platforms and can be used with TypeScript and JavaScript (ES2023). Its goal is to always support the latest JavaScript features and provide additional features that help you to develop any kind of application that uses databases from small applications with a few tables to large scale enterprise applications with multiple databases. TypeORM supports more databases than any other JS/TS ORM: Google Spanner, Microsoft SqlServer, MySQL/MariaDB, MongoDB, Oracle, Postgres, SAP HANA and SQLite, as well as…
read the full typeorm overview →
About JSqlParser
JSqlParser Turn any SQL statement into a traversable tree of Java objects and back again. An RDBMS agnostic SQL parser for the JVM: one grammar, twelve dialects, no native extensions. Website · Samples · Syntax · Change Log · Contributing What it does Give it SQL. Get an AST you can walk, rewrite, and print back out. The tree is traversable with the Visitor pattern, and the same object model works in reverse: build statements from Java with a fluent API and render them as SQL text. Install Use the stable Manticore builds . They are released continuously from the current development line and carry all of the…
read the full JSqlParser overview →
More in Infrastructure & Operations
Related comparisons
More Databases projects
Compare either of these against the rest of the Databases field.
Frequently asked questions
Is typeorm or JSqlParser more popular?
typeorm has 36,661 GitHub stars and JSqlParser has 5,970. typeorm has the larger community by that measure.
Are typeorm and JSqlParser free?
Both are open source. typeorm is licensed under MIT and JSqlParser under Apache-2.0. Neither carries a licence fee.
What is the difference between typeorm and JSqlParser?
typeorm is written in TypeScript and JSqlParser in Java. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, typeorm or JSqlParser?
Choose typeorm if you want the larger community (36,661 stars) or its MIT licence terms. Choose JSqlParser if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.