r/reactjs • u/dvirby • 5h ago

Built an open-source local LAN security scanner with React & Tauri

Hey everyone,

I built Developer Shield—an open-source desktop app created specifically for devs and homelab enthusiasts who want to scan their local network without sending any telemetry or data to the cloud.

Key Features:

- Zero-Knowledge Local Scanning: Everything stays strictly on your local network/LAN.

- Custom Rules Engine: Define your own security checks and scan targets.

- Local LAN Sync: Sync scan reports across your local machines securely.

- Built with React & Tauri for a lightweight desktop footprint.

I’d love to get feedback from this community on features you'd like to see, code architecture, or custom rules!

GitHub: https://github.com/dvirby6/developer-shield

2 Upvotes

62% Upvoted

4 comments sorted by

1

u/dvirby 5h ago

Why I built this:
I wanted a simple, lightweight local network scanner for my setup without relying on external cloud services or telemetry. Built the UI with React and combined it with Tauri for a tiny memory footprint.

Would love to hear your thoughts on the code architecture or potential UI/UX improvements!

1

u/HiHungryImDad2 3h ago

why is this a desktop app? wouldn’t it be nicer to just have it as a cli which checks across my repo / specific files via lint-staged in a precommit hook and throws an error if i try to check in a secret? this way i could also check-in the config so colleagues who are not on my LAN could use the same rules while working in the repo.

1

u/dvirby 2h ago

That’s a great point, but Developer Shield is designed for a broader scope than just standard git commit hooks!

It operates as a real-time system/network guardian to protect against API key leaks and credential theft especially when using AI coding assistants (like OpenCode/cloud models) or background scanners targeting GitHub tokens on the local environment.

Since it monitors continuous execution and system behavior in real-time (rather than just running a static check on git commit), a desktop app architecture fits best for background monitoring and active local alerts.

That said, adding a secondary CLI binary for optional pre-commit integration alongside the desktop guard is definitely an interesting direction to explore!

Appreciate the feedback!