Postgres vs SQLite Npx
Postgres scores 36 points higher on the same evidence, which is a real separation rather than noise. Both are measured the same way, on the same day, from public evidence only — so this is a comparison of two measurements rather than two marketing pages. How we measure ›
| Postgres | SQLite Npx | what it means | |
|---|---|---|---|
| tashan score | 74 | 38 | upkeep + freshness, gated by adoption |
| Adoption evidence | 2k/wk | 3k/wk | the raw public signal the score came from |
| Last release | active | abandoned | npm publish or repo push |
| Upkeep | 87 | 44 | cadence, maintainers, status |
| Expertise grade | solid | not graded | an LLM read of its own documentation against a fixed rubric |
| Security audit | no known advisories, runs an install script, no build provenance | no known advisories, no build provenance | existence of findings is always free; the detail a licence buys is on each dossier |
| Licence | AGPL-3.0 | ISC | |
| Maintainers | more than one | one primary | bus-factor risk |
Install either
Postgres
claude mcp add henkey-postgres-mcp-server -- npx -y @henkey/postgres-mcp-serverSQLite Npx
claude mcp add mcp-server-sqlite-npx -- npx -y mcp-server-sqlite-npxNeither score is a security verdict — "well maintained" and "nothing known is wrong" are different claims, which is why the audit is a separate row and never folded into the number. The full audit for each, including what a licence adds, is on its own page: Postgres · SQLite Npx.