DevTools-X: 41 Offline Utilities in a Tauri Shell, and What Its README Admits
Collection of offline first developer utilities available as non-electron desktop application. all in one place, cross-platform, 10MB app!
At a glance
- What is it?
- DevTools-X bundles 41 developer utilities into a roughly 10MB Tauri desktop app that runs on Linux, macOS and Windows. The pitch is a single offline toolbox; the README itself flags uneven testing across platforms and a regex tester the maintainer calls broken.
- Who is it for?
- Adopt DevTools-X if you want one offline binary covering JSON formatting, JWT decoding, hashing, image compression and similar chores on Linux, macOS and Windows, and you are willing to file bugs when a module misbehaves on your platform. Do not adopt it if you need a signed macOS build, guaranteed per-module test coverage, or a working regex tester today, since the README states the regex module is 'kinda broken'.
- 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 109 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 September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The gap DevTools-X fills between DevUtils and DevToys
The README opens with the problem in one line: devutils is macOS-only and devtoys is Windows-only. Anyone working across Linux, macOS and Windows ends up either switching tools per machine or maintaining two habits. DevTools-X is the maintainer's answer, a cross-platform, non-Electron collection of developer utilities. The acknowledgement section says the project exists because the author was 'fed up switching between different tools on different OSes', and both DevUtils and DevToys are credited as inspiration for individual modules.
The intended user is a working developer who needs small conversions and inspections without opening a browser tab or a full IDE: format JSON, decode a JWT, hash a file, compress an image, generate a UUID. The README lists 41 modules and says the count is growing. The audience is narrow on purpose. This is not a platform, a library or a service. It is a desktop app you install once and open when a task takes thirty seconds.
Tauri, Rust and Monaco: what the architecture actually buys
The tech stack section is explicit: client is React with Mantine, backend is Rust, and the app is built on Tauri. The README states plainly that DevTools-X is 'NOT WRITTEN IN ELECTRON', and the stated benefit is bundle size, with the installer described as about 10MB.
Work is split by sensitivity and cost. The FAQ says many modules are written in pure JavaScript, and that Rust is used only where performance or security matters, naming hash calculation and image compression as examples. The feature list backs this up: bulk image compression is described as using Rust SIMD, while something like the color converter or the number converter has no reason to leave the web layer. That split is the main architectural decision in the project, and it is a reasonable one. A hash or a compression pass over a large file in JavaScript would block the UI thread or need a worker; doing it in Rust keeps the web view responsive.
The other decision is the editor. The README calls the use of monaco-editor, the editor from VS Code, 'one big selling point', and says editor features are available as if you were using VS Code. That matters for the JSON formatter, the SQL formatter, the diff tool and the scratchpads, because syntax highlighting and large-document handling come from Monaco rather than from hand-written text areas. It also has a cost, which shows up later in the README's own bug list.
Installing it: prebuilt binaries, an unsigned macOS app, and a build from source
The primary path is the Releases page. The README says a GitHub CI builds binaries for all platforms and that you download the binary for your system. For macOS there is a required extra step, because the README states the binaries are not signed yet:
xattr -r -c /Applications/devtools-x.app
That command clears extended attributes recursively on the app bundle, which is the standard way around Gatekeeper quarantine for an unsigned build. The README does not describe notarisation or a signed build, so treat this as the current state rather than a temporary note.
Building from source is a two-step process in the README. First install the Tauri prerequisites, which it points to at the tauri.app v1 prerequisites page. Then clone the repository, open a terminal in it, and run:
yarn tauri build
That is the whole documented build. There is no separate step for installing Node dependencies, no environment file, and no configuration key mentioned for the build itself. The only configuration file discussed anywhere is settings.json, which lives in the Tauri app data directory. The README links to the Tauri path API documentation for locating that directory rather than hardcoding a path, which is the right call given three target platforms.
Two recovery procedures are documented for settings.json. If the app does not render or load anything, the README says to delete the file if it exists, or create it if it does not. If the app will not start or shows an empty screen, the README says the database is most likely corrupt and the fix is the same: delete settings.json in the app data directory. Module order is also stored there, and the README notes it is a simple JSON file you can edit by hand, in addition to the drag-and-drop reordering in the UI. Backup and restore are available in the settings drawer.
The module list is the product, and it is uneven by design
Forty-one modules in one binary is the entire value proposition, so the list is worth reading as a map of what you get. It divides into a few clusters. Text and data conversion covers Base64 text and images, JSON formatting and minification, YAML to JSON, number conversion, unit conversion for length and pressure, URL parsing, and text gzip, deflate and zlib compression. Crypto and identity covers MD5 and SHA text hashing, file MD5, HMAC generation, JWT decoding, and two password generators, one of which is stateless. Web work covers a basic REST client, a QR code generator and reader, HTML editing and preview, CSS live playground, Markdown editing and preview, a React live scratchpad, and a multi-language programming scratchpad. Media covers image compression and conversion with preview, bulk image compression, and an image cropper. There is also a PDF reader, a cron editor with explanation, a regex tester, a Faker-based mock data generator, a code and text diff with syntax highlighting, a color picker and converter, a color palette generator, and color harmonies.
The honest part is the note at the top: the application is stable, but there are too many modules and they are not all well tested on all three operating systems. The maintainer asks for bug reports. That is a fair description of what a solo-maintained toolbox of this size looks like. Breadth was chosen over uniform polish, and the README does not pretend otherwise. If your work depends on one specific module, the relevant question is whether that module behaves on your OS, and the README cannot answer that for you.
Known breakage: Tauri v2 migration, CSS regressions, and a regex tester the README calls broken
The limitations are stated by the project itself, which makes them easy to weigh. After migrating to Tauri v2, the README says the app is facing minor bugs again because of Tauri, and that you might see basic CSS breaking or the app not working on a specific platform. The phrasing 'because of tauri' places the cause in the framework migration rather than in the module code, and the maintainer commits to fixing what can be fixed on their side. Read that as a warning that the current release line has known rough edges on some platforms, not as a claim that everything is fine.
The second admission is more specific and more useful. Under a section headed 'NEED HELP WITH', the README lists 'Regex Tester is kinda broken, monaco gives a headache'. So the module that many developers would reach for first is, by the maintainer's own account, not reliable, and the cause is the Monaco integration rather than the regex engine. The same section asks for help with more features, testing, logo improvements, and fixing all FIXME and TODO comments in the codebase. A project listing 'testing' as an area where it needs help tells you what to expect from the CI beyond build artifacts.
The practical consequence: DevTools-X is the wrong tool if you need a dependable regex workbench, and it is the wrong tool if you require signed macOS binaries, since the README instructs you to run xattr yourself. It is also the wrong choice if you want a single-purpose utility with a narrow, well-tested surface. The 41-module bundle is the feature and the risk at the same time.
How it differs from DevToys and DevUtils in approach
The two projects credited in the acknowledgements take a different route. DevUtils is macOS-only and DevToys is Windows-only, according to the README's own framing. Choosing either one means accepting a platform lock, and on the other two operating systems you find something else. DevTools-X spends its complexity budget on portability instead: one Tauri codebase, React and Mantine for the interface, Rust for the heavy operations, and CI producing binaries for Linux, macOS and Windows.
That trade has a visible cost. A Windows-only tool can lean on native Windows APIs and ship a signed installer without a cross-platform signing story. A single codebase has to keep three platforms working through one framework, and the README's note about Tauri v2 regressions is exactly that cost showing up. The Electron-based alternative, which the README implicitly positions against by stating the app is not Electron, would give a more predictable rendering story across platforms at the price of a much larger installer. DevTools-X bets that a roughly 10MB Tauri bundle and Rust-backed operations are worth the occasional platform-specific breakage. Whether that bet pays off depends on which modules you use and on which OS.
Maintenance, licensing and what to check before you rely on it
The licence is MIT, stated in the README and shown as a badge. That is permissive: you can use, modify and redistribute the code, including in commercial settings, provided the licence terms are met. This is a description of the licence identifier, not legal advice, and anyone embedding the project in a product should read the MIT text and their own obligations rather than rely on a summary.
Maintenance signals from the repository metadata are mixed but not alarming. The project is not archived, the default branch is master, and the last push is recent. Releases are tagged in a devtoolsx-vX.Y.Z pattern, with v3.4.1 dated 2025-01-05, preceded by v3.3.3 and v3.3.2 in November 2024. The gap between the last release and the last push suggests development continues between tagged builds. The README's call for help with testing, features and FIXME cleanup indicates a small contributor base, which is the main upgrade-cost consideration: you are depending on a project that asks for testers.
Upgrade cost itself is low by design. Settings live in a single settings.json in the app data directory, module order is stored in that same JSON file and can be edited by hand, and the settings drawer offers backup and restore. Moving between versions means keeping that file; recovering from a bad state means deleting it. The macOS xattr step has to be repeated for each new unsigned build you install. If you build from source, the Tauri prerequisites are the recurring setup cost, and the build command does not change.
What to verify first is concrete. Install a release build, clear the quarantine attribute on macOS, and open the specific modules your work depends on rather than trusting the module count. If a module fails, the README's own recovery path is to delete settings.json in the Tauri app data directory and restart. If it still fails, that is the bug the issue tracker is asking for.
Editorial conclusion
Adopt DevTools-X if you want one offline binary covering JSON formatting, JWT decoding, hashing, image compression and similar chores on Linux, macOS and Windows, and you are willing to file bugs when a module misbehaves on your platform. Do not adopt it if you need a signed macOS build, guaranteed per-module test coverage, or a working regex tester today, since the README states the regex module is 'kinda broken'. Before committing, run yarn tauri build from a clone and open the modules you actually depend on, especially on macOS where the README requires xattr -r -c /Applications/devtools-x.app after installation.
Community notes