DEV Community: Karthick Ajan G S

Stop using external npm packages just to generate a UUID v4

Karthick Ajan G S — Mon, 25 May 2026 06:25:00 +0000

For years, the go-to move for generating a UUID in Node.js or the browser was installing the uuid package.

But if you are targeting modern environments, you can ditch the extra dependency entirely. Modern browsers and Node.js (19+) have native cryptographic support built right into the crypto global module.

Here is how you generate a cryptographically secure UUID v4 natively:

// Native Web Crypto API (Runs in browser and modern Node.js)
const uuid = crypto.randomUUID();
console.log(uuid); // e.g., "f81d4fae-7dec-11d0-a765-00a0c91e6bf6"

Why this matters for security
Unlike old-school math-based pseudo-random generators (⁠Math.random()⁠), ⁠crypto.randomUUID()⁠ uses the underlying operating system's hardware-backed entropy. It's fast, secure, and doesn't bloat your production bundle.
Need to generate UUIDs on the fly?
If you just need a batch of secure keys for configuration files, database testing, or environment variables, stop pasting your requirements into third-party online generators that process data on backend servers.
I built a completely offline, zero-server utility to generate these instantly in your browser:
👉 Secure Browser UUID Generator
It runs 100% client-side via the Web Crypto API, meaning your generated IDs never touch a network loop. Part of a larger privacy-first suite of tools at cipherkit.app.

Anyone willing to join me ?

Karthick Ajan G S — Sun, 12 Apr 2026 22:22:06 +0000

Karthick Ajan G S

Apr 6

CipherKit

#showdev #webdev #opensource #security

Comments

2 min read

CipherKit

Karthick Ajan G S — Mon, 06 Apr 2026 15:27:23 +0000

I built 77 free developer tools that run 100% in your browser (No tracking, no backend)

Hey DEV community 👋

If you are anything like me, you've probably had that moment of hesitation right before pasting a JWT, an AES key, or a proprietary JSON payload into a random online formatter.

Is this site logging my input? Is there a backend saving this?

I got tired of the paranoia, so I spent the last few months building CipherKit.

👉 [Live Site: https://cipherkit.app/)
👉 GitHub Repo (I'd love a star if you find it useful!)

What is CipherKit?

It is a unified suite of 77 developer utility tools. But the core rule of the project is simple: Everything must be 100% client-side.

There is no backend. There is no database. No login is required. The calculations, encryptions, and formatting happen entirely within your browser's memory using vanilla JS and the Web Crypto API. Your data never leaves your device.

What's inside the toolkit?

I split the tools into 5 main hubs to keep things organized:

🗝️ Crypto Hub: AES Encryption/Decryption, SHA-256/512 Hashing, RSA Key Pairs, Bcrypt, JWT Builder, and TOTP generation.
🔗 Encoding Hub: Base64 (Standard & URL-safe), URL, HTML Entity, Hex, and Binary encoders/decoders.
🔄 Converter Hub: Instant XML↔JSON, YAML↔JSON, CSV↔Excel, and Markdown↔PDF transformation.
💻 Dev Hub: UUID Generator, interactive Regex Tester, Cron Expression Builder, SQL Formatter, and a professional-grade Text Diff & Merge workspace.
🖼️ Image Hub: QR Code generation, SVG↔PNG conversion, multi-format Image Resizers, and color code utilities.

The Tech Stack

To keep it fast and secure, it's built with pure HTML, CSS, and JS, and hosted for free on GitHub Pages. No heavy frameworks, just instant load times.

Feedback Welcome!

Since this is built for developers, I would love to hear your thoughts.

What tools are missing from your daily workflow?
Do you catch any edge cases in the crypto implementations?
What would make you bookmark this?

Drop a comment below or open an issue on the repo!