Sqlectron's README is a page of links, and the binaries come from another repo
A simple and lightweight SQL client desktop with cross database and platform support.
At a glance
- What is it?
- Sqlectron is an Electron SQL client written in TypeScript, packaged as a dmg, six Linux formats and an nsis installer. The database list and the released artifacts each live in a separate repository, which is the main fact an adopter has to plan around.
- Who is it for?
- Sqlectron fits someone who wants a desktop SQL client they can install from a signed installer and whose database support they will verify in the sqlectron-core list first. It does not fit someone who wants this repository to be the source of truth: the README is a short page of links, the supported database list is maintained elsewhere, and the released artifacts come from sqlectron-gui.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 146 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- sqlectron/sqlectron4,757 ★ · +0
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| sqlectron/sqlectron | 4.8k | 4.8k |
0 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
An 85 word page that only links elsewhere
The whole front page is a short paragraph, a heading reading Demo (version 1.0.0), six links and a pronunciation note. It is pronounced sequel-eck-tron, which tells you what the maintainers think the name should sound like and nothing about the software. The six links do the actual explaining: Databases for the list of current supported databases, Download for installers, binaries and source, Configuration for the file holding saved servers and custom configurations, App Docs for helper docs about the app, Terminal for a terminal based interface, and Contribute for how to help. Meanwhile package.json declares version 1.39.0, so the demo label on the page is describing artefacts from a much earlier line of the project. Nothing on this page explains a feature, shows a query, or gives an install step. A reader has to follow a link before learning anything.
Download and package metadata both point at sqlectron-gui
The Download link does not point here. It points at the releases of a different repository, sqlectron-gui, described as installers, binaries and source. The package metadata agrees with that link rather than with the directory name: the repository field in package.json is sqlectron-gui, and so is the bugs field. This repository is where the application source lives, not where the packaged application is published. Two consequences follow. If you want an installer, you are downloading from sqlectron-gui, and its release history is the one to watch. If you find a defect in a shipped build, the metadata points you at a different issue tracker than the code you are reading. The entry point in package.json is `./out/browser/main.js`, which is also a built artefact rather than a source file, so nothing in this tree runs without a build step first.
The supported database list is maintained in sqlectron-core
Cross database support is the headline claim in the project description, and not one database name appears in the README. The Databases link resolves to the current supported databases section of the sqlectron-core readme, so the coverage matrix lives with the core package rather than with the desktop app. That split is sensible for a codebase that separates the core engine, the GUI and the terminal interface, and it also means the answer to the first question anyone asks, which databases does it speak to, cannot be answered from this page at all. The same pattern applies to the terminal interface: sqlectron-term is a separate repository. Three repositories, and a top level page whose job is to point at all three.
Build targets cover dmg, six Linux formats and nsis
The packaging matrix is the most concrete thing in package.json. macOS builds a dmg for x64 and arm64, with hardenedRuntime set to true, notarize set to true, gatekeeperAssess set to false and an entitlements plist used both for the app and for its inherited children, plus an afterPack hook. The DMG layout places a link to /Applications and a file slot at fixed coordinates. Linux is configured with six targets:
"linux": {
"target": [
"deb",
"rpm",
"freebsd",
"pacman",
"tar.xz",
"tar.gz"
]
},Windows uses an nsis target for x64 and ia32, signed through Azure with the publisher name Matthew Peveler and a certificate profile named Sqlectron. Two details are worth noticing for planning: ia32 is still listed next to x64, and there is no AppImage target in the list.
The container image produces Windows packages only
Both the Dockerfile and docker-compose.yml define the same single dist service, and the reason is written in a comment rather than left to be discovered:
FROM maxcnunes/electron-distribution:eb3node4-onbuild
ENV TMPDIR /usr/src/app/.tmp
CMD ["npm", "run", "--unsafe-perm", "dist:winlinux"]The compose file adds a TMPDIR environment variable of the same value and mounts the project directory at /usr/src/app. The task is build all and pack only for Windows, because packing for macOS from Linux is not possible, and the command is `npm run --unsafe-perm dist:winlinux`, with unsafe-perm there to force npm to respect the tmp path. TMPDIR is deliberately kept inside the project so cache files survive between distribution runs. In practice this means a Linux container is a Windows packaging machine, not a general build environment, and the macOS dmg has to be produced on a Mac.
A web pipeline wraps the desktop application
The tree is a web toolchain wrapped in Electron packaging. There is webpack.config.js, babel.config.js, postcss.config.js and tailwind.config.js for the asset pipeline, a .storybook/ directory with a stories/ folder for interface components, and eslint.config.js with .prettierrc.json, .prettierignore and .lintstagedrc.json plus a .husky/ directory for commit time checks. Tests run through two vitest configurations, vitest.config.mts and vitest.e2e.config.mts, so unit and end to end runs are separate commands. TypeScript has tsconfig.json and tsconfig.build.json, and there is a vendor/ directory plus an empty-shim.js at the root. The consequence is that a dependency bump in the web stack, the bundler, the CSS framework or the component workshop is a packaging change as much as a code change, and the Electron version that everything ships inside is not visible anywhere on this page.
One release in 2025 after a three year gap
The release history explains why the demo label on the page still says 1.0.0. Version 1.38.0 was published on 2022-03-31, with 1.38.0-alpha.3 before it on 2022-02-01, and then nothing until v1.39.0 on 2025-12-03. That is a gap of more than three years between the two stable tags, and the version field in package.json still reads 1.39.0, so the manifest has not moved past the newest tag. The last push to the default branch, main, was on 2026-06-22, which is months after the tag. The repository is not archived, so work continues, but nobody on this page promises a release cadence, and a change sitting on main may never appear in an installer. The licence is MIT, recorded in the LICENSE file at the top level and in the package metadata.
Editorial conclusion
Sqlectron fits someone who wants a desktop SQL client they can install from a signed installer and whose database support they will verify in the sqlectron-core list first. It does not fit someone who wants this repository to be the source of truth: the README is a short page of links, the supported database list is maintained elsewhere, and the released artifacts come from sqlectron-gui. Before you rely on it, check the release history, where the newest tag is v1.39.0 from 2025-12-03 while the last push to main was on 2026-06-22, so an unreleased main branch is ahead of any installer, and read the configuration file documentation for where saved servers are stored.
Frequently asked questions
How do I install Sqlectron on Windows?
The Download link on the page points at the sqlectron-gui releases, which it describes as installers, binaries and source. In package.json the Windows target is an nsis installer for x64 and ia32, code signed through Azure with the publisher name Matthew Peveler and a certificate profile named Sqlectron.
Which databases does Sqlectron support?
No database is named in the README. The page links the list of current supported databases to sqlectron-core, so driver coverage is maintained in that repository and may differ from what any given release of the app was tested against.
Does Sqlectron have a terminal interface?
Yes, a terminal based interface lives in its own repository, sqlectron-term, linked from the main page under the Terminal heading. This repository holds the desktop application.
Where does Sqlectron store saved servers?
Saved servers and custom configurations live in a configuration file, and the page links the details to docs/app/configuration-file.md. Helper documentation about the app sits alongside it under docs/app.
Which platforms does Sqlectron ship for?
The build matrix in package.json lists a dmg target for macOS on x64 and arm64, Linux targets of deb, rpm, freebsd, pacman, tar.xz and tar.gz, and an nsis target for Windows on x64 and ia32. A Linux container can package Windows builds but not macOS ones.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/sqlectron-sqlectron)Star history chart for your README
[](https://hysenlabs.com/projects/sqlectron-sqlectron)Was this useful?