Menu

Why I built Dev Tools that runs entirely on the browser
📰

Why I built Dev Tools that runs entirely on the browser

DEV Community: webdev·Nikhar Minds·4 days ago
#ZJOZnhip
#devtowebdev#devto#dev#tools#sites
Reading 0:00
15s threshold

Hello everyone, this is my first post here and I will admit something: I used to paste the production JWTs into the first JWT decoder google gave me. Same with the Crontabs, with CSV exports full of customer data. Then one day, I was doing a security training targeted for the Security Controls and realized I am doing something really wrong here. Because I didn't know where that data went when I pasted in those online sites.

Most online dev tools works the same way. Broswer sends input to an API, then a Server parses it and result comes back. But somewhere in between, it can end up in logs, analytical pipelines, load balancer records, or may be just in their database.

So I started looking into multiple online tools which doesn't save our data and works only on the client side. There are few sites which does that but for every utility, we need to visit different sites and not all of them promote the 100% client side, or no data logged terms. So we never know.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.