head to head · open source

orm vs JSqlParser

orm has 47,661 GitHub stars, 2,605 forks, 2,627 open issues and last shipped 2 days ago. JSqlParser has 5,970 stars, 1,446 forks, 12 open issues and last shipped 5 days ago. orm leads on adoption by 698% (47,661 vs 5,970 stars). orm is written in TypeScript under Apache-2.0; JSqlParser is written in Java under Apache-2.0. orm has attracted 5% as many forks as stars, JSqlParser 24%. orm was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (mysql), 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.

orm ★ 48K JSqlParser ★ 6.0K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

orm JSqlParser
GitHub stars ★ 48K ★ 6.0K
License Apache-2.0 Apache-2.0
Written in TypeScript Java
Last push 2026-11-03 2026-10-31
Forks ⑂ 2.6K ⑂ 1.4K
Self-hosting Yes Yes
Data ownership Your server Your server

pick orm if

  • You weight community size — 48K stars and counting
  • You want the Apache-2.0 license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full orm profile →

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

full JSqlParser profile →

About orm

Docs Discord X Blog Post Architecture Using Prisma 7? It remains fully supported. Its source lives on the v7 branch of this repository and its docs at prisma.io/docs/orm/v7. Prisma 8 is a release candidate. 8.0.0 final is expected in the next four to eight weeks. Until then a release candidate may include breaking changes, and every release ships with an upgrade recipe that the prisma 8 skill applies for you. The candidate is a complete implementation we stand behind: we treat bugs in it as urgent, and the risk you take on is a feature that is not built yet rather than churn. The feature scoreboard names every…

read the full orm 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 orm or JSqlParser more popular?

orm has 47,661 GitHub stars and JSqlParser has 5,970. orm has the larger community by that measure.

Are orm and JSqlParser free?

Both are open source. orm is licensed under Apache-2.0 and JSqlParser under Apache-2.0. Neither carries a licence fee.

What is the difference between orm and JSqlParser?

orm 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, orm or JSqlParser?

Choose orm if you want the larger community (47,661 stars) or its Apache-2.0 licence terms. Choose JSqlParser if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.