// the find
lissy93/networking-toolbox
🛜 100+ offline-first networking tools and utilities
A Svelte/SvelteKit app that bundles 100+ networking calculators and generators (CIDR math, DNS record builders, DHCP options, IPv6 tooling, DNSSEC helpers) into one offline-capable site you can self-host or run as a static page. Aimed at sysadmins and network engineers who want a single reference tool instead of bookmarking a dozen scattered calculator sites.
The breadth is real, not padding — src/lib/utils has dozens of pure, independently testable functions (cidr-split, dhcp-option121, dnssec, eui64, etc.) each paired with its own component and content file, so the pattern is consistent across 100+ tools rather than one-off hacks. It's not just a UI toy: several tools are also exposed as API routes (api/cidr/[tool], api/dns/[tool]), so you can hit the same logic programmatically. Test setup is actually used, not just declared — Vitest unit tests, a separate API test suite, Playwright e2e, coverage reporting, and CI (check.yml, tests.yml) gating merges on lint/types/svelte-check/build. Deployment flexibility is implemented, not aspirational — DEPLOY_ENV switches real SvelteKit adapters (node/static/vercel/netlify/docker), so Docker, GitHub Pages, and static hosting are all genuinely supported paths, not just README suggestions.
At 100+ independently-implemented calculators, correctness auditing is a real risk — DNSSEC/NSEC3/DUID-style tools are easy to get subtly wrong, and there's no visibility into per-tool test coverage vs. a single aggregate coverage number. The README's 'zero third-party dependencies' claim doesn't hold up — it's a full SvelteKit app with an npm dependency tree; that's the kind of marketing line the project itself would probably flag in someone else's README. There's no plugin or registration system for adding tools — the existence of a dedicated .github/docs/new-tools.md guide suggests wiring a new tool still means manually touching a component, a util file, a content file, and nav config. And for a toolbox that's fundamentally client-side math, packaging it as a Docker container to self-host feels heavier than necessary when a static host would do the same job for most users.