How dstotijn/hetty works
Project type and purpose
• Hetty is a full-stack HTTP toolkit for security research. It runs as a single CLI-launched process that:
• Acts as a man-in-the-middle (MITM) HTTP proxy.
• Hosts a GraphQL API.
• Serves a Next.js-based web admin interface.
• Users point their browser or tools at the proxy, then use the web UI to inspect, edit, replay, and search HTTP traffic.
File structure
• Top-level “cmd/hetty”: Go code for CLI entrypoint, proxy instantiation, server wiring.
• “pkg/…”: Core Go libraries for proxy (pkg/proxy), database (pkg/db/bolt), filtering (pkg/filter), request logging (pkg/reqlog), scope and sender logic, Chrome helper integration.
• “pkg/api” + “gqlgen.yml”: GraphQL schema, generated types, resolvers back the web UI.
• “admin/”: Next.js React app (TypeScript) powered by Apollo-GraphQL, with features under “features/…”, shared components under “lib/…”, and pages under “pages/…”.
• Config/build files: Dockerfile, Makefile, gqlgen.yml, Go module files, workflows for CI.
README insights
• Confirms triad of proxy / GraphQL / web UI.
• Notes embedded Bolt DB for per-project storage.
• Describes key features: intercept, scope, sender, HTTP request logs, project isolation.