Dev.to WebDev 🛠 Dev 👁 0 📖 3 min read

I audited 40 side projects. What I removed mattered more than what I built.

I audited 40 side projects. What I removed mattered more than what I built. In November 2026 I stopped building for a couple of weeks and went through every app on hylst.fr, one by one. I expected bugs. I found promise

I audited 40 side projects. What I removed mattered more than what I built.

In November 2026 I stopped building for a couple of weeks and went through every app on hylst.fr, one by one. I expected bugs. I found promises my code wasn't keeping.

Why I did this

I have around 40 apps and websites. They grew out of curiosity over several years, not out of a plan. That's a nice way to build and a terrible way to maintain. By mid-November I had enough small interruptions to know I needed a full pass.

I'll be honest: I'm not a security expert. I'm a self-taught developer with a thing for making tools that stay out of your way. What I did was simple, almost boring: open each app, read the text on the screen, then read the code behind it, and compare the two.

1. Dependencies: no critical findings, but that's not luck

On 16 November, zero critical, high or moderate vulnerabilities in production across the menu (Guide Maths, À votre service, HylstDevToolBox, DataLab, Next.js 16.4.6...).

That number only means something with the work behind it: going through libraries app by app, updating what needed updating, removing what nobody used. It's not a badge. It's hygiene.

2. Secrets that shouldn't survive a tab close

  • DataLab: remote API keys no longer survive closing the tab.
  • HylstDevToolBox: clipboard history is gone on close.
  • À votre service: generated passwords no longer sit in plain text in the browser.
  • Guide Maths: the notepad now stores a PBKDF2 hash, 210,000 iterations.

None of this is clever. It's just the difference between "we don't store your data" and actually not storing it.

3. Cutting the external calls

No more Google Fonts or Unsplash calls. In Brevet, a student's nickname no longer leaves the browser to generate an avatar; it's drawn locally. CSP policies per section, legal notices everywhere.

4. The honesty pass (this was the hard one)

In À votre service I removed 27 mentions of encryption or cloud sync that the code wasn't doing yet. All 87 tools were checked one by one.

On Bulle Sensorielle I deleted every "therapeutic" claim. It's a relaxation tool, not a medical device. Let's call a cat a cat.

I wrote those words. Nobody forced me to. They were optimistic descriptions of things I intended to build. That's not a small thing when someone types a password into your tool.

5. The funny bits

An audit always turns up something ridiculous:

  • Brevet's profile save had been silent since June because of a circular import nobody saw.
  • The React quiz had got into the habit of quietly overwriting the Java quiz's progress. Territory war in the browser.
  • 3D Creator's service worker thought reloading the page mid-use was a good idea.

All back in order.

What I'd tell someone doing the same

Every deploy is now rebuilt from a clean clone and checked with browser scenarios across 49 sections. That's the real fix: not the one-time cleanup, the thing that stops the dust coming back.

Three rules I'd keep:

  1. Check the text against the code, not the other way around.
  2. Delete a promise before you implement it, not after.
  3. If it can stay in the browser, keep it in the browser.

Nothing magical here. Just rigour and digital hygiene so these tools stay reliable, sober and respectful of the people using them.

What's the most surprising thing you found during your own cleanup?

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.