A · leads
typeorm
96.5
36,674 stars · MIT
Databases
typeorm leads by 3.2 · narrow
A · leads
96.5
36,674 stars · MIT
B
93.3
27,730 stars · BSD-3-Clause
typeorm versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. typeorm is written mainly in TypeScript; Valkey is written mainly in C. The composite score is 96.5 for typeorm and 93.3 for Valkey.
typeorm has 36,674 GitHub stars to Valkey's 27,730, a gap of 8,944 (1.32×). Forks are 6,695 for typeorm and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 83.
Push history: typeorm was last pushed on 17 November 2026 (0 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 749 for typeorm (0.020 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
typeorm is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Valkey is listed as BSD-3-Clause, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for typeorm and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both typeorm (36,674 stars) and Valkey (27,730 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: typeorm is open source, Valkey is open source.
typeorm is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 17 points (100 vs 83), and the tightest is self-hosting at 0 points (100 vs 100).
typeorm finishes ahead at 96.5 against Valkey at 93.3, a 3.2 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | typeorm | Valkey |
|---|---|---|
| GitHub stars | 36,674 | 27,730 |
| Forks | 6,695 | 1,540 |
| Open issues | 749 | 1,045 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 83 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 93.3 |
TypeScript & JavaScript ORM for Node.js — supports PostgreSQL, MySQL, MariaDB, SQLite, SQL Server, Oracle, and more.
Valkey is a Linux Foundation key-value store forked from Redis. It is used as a cache, queue, and ephemeral data store under a permissive license.
typeorm has more GitHub stars: 36,674 versus 27,730 for Valkey. The gap is 8,944 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both typeorm and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
typeorm is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Valkey is listed as BSD-3-Clause, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
typeorm scores 96.5 and Valkey scores 93.3. This page calls that a narrow lead for typeorm.