Add GPL-3.0 license

LICENSE is the exact, unmodified canonical text from gnu.org (fetched
directly, verified byte-identical via checksum before adding - a
license file is exactly the kind of text where reproducing it from
memory risks a subtle, avoidable error, so it wasn't worth the risk
when the authoritative source is one curl away). Per the GPL's own
guidance, the license document itself stays verbatim; the copyright
notice goes separately in README instead of scattered across every
source file's header, keeping this a one-place, low-noise addition
rather than a 30-file mechanical edit nobody asked for.

GPL-3.0 chosen deliberately for a security tool: it keeps derivatives
open (a vendor can't take community security tooling proprietary),
which is a common and well-regarded choice in that specific community.
Doesn't foreclose monetization either - as sole copyright holder,
dual-licensing the code commercially to others separately from the
public GPL release remains available, and the choice itself stays
changeable in the future for the same reason: relicensing only gets
hard once other people's copyrighted contributions are in the
codebase, which isn't the case here yet.

1 files changed, 6 insertions, 0 deletions

diff --git a/README.md b/README.md
index 7173984..393b0bc 100644
--- a/README.md
+++ b/README.md
@@ -463,3 +463,9 @@ reasoning behind each:
   SOCKS5
 - No active or passive vulnerability scanning, no plugin system - this
   is a manual-testing tool, not a scanner
+
+## License
+
+GPL-3.0. See [LICENSE](LICENSE).
+
+Copyright (C) 2026 srdusr