mitmproxy / mitmproxy

GitHub metadata describes the project as an interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers, with the homepage mitmproxy.org.

GitHub topics include http, http2, proxy, tls, ssl, websocket, security, debugging, python and mitmproxy, and the primary language is Python.

Language byte counts put Python first at about 2.77 MB, followed by TypeScript (about 521 kB), JavaScript (about 119 kB), Less (about 50 kB) and CSS.

The repository is MIT-licensed; the latest recorded release is v12.2.3 (published 2026-05-12), with 45,046 stars recorded at the 2026-09-14 snapshot.

Structurally, the analyzer grouped the tree around four top-level subsystem directories — docs, mitmproxy, test and web — alongside examples, release and .github directories.

mitmproxy/tools/main.py and mitmproxy/tools/web/app.py are flagged as likely executable entrypoints by a filename heuristic.

web/package.json defines a start script that runs vite.

The packet records 25 Python files with __main__ guards, including release/build.py, release/deploy.py, release/release.py, mitmproxy/version.py (whose guard prints VERSION), mitmproxy/proxy/server.py and docs/scripts/clirecording/record.py. release/build.py's guard calls cli():

if __name__ == "__main__":
    cli()

The six execution paths listed in the packet (five from docs/scripts/clirecording/record.py, where a CliDirector drives screenplays that record the user interface and intercept, modify and replay requests, and one from examples/contrib/mitmproxywrapper.py) each end at an external/unresolved boundary; the packet's maturity signals separately report 245 bounded execution paths overall.

The analyzer's inferred summary calls mitmproxy/version.py the apparent main starting place, while the filename heuristic points to mitmproxy/tools/main.py; both are static hints rather than established launch flows.

The analyzed tree holds 1292 files: 285 under mitmproxy/, 427 under test/, 286 under web/, 166 under docs/, 73 under examples/ and 33 under release/.

Static relation extraction produced 33086 edges — 28836 calls and 4250 imports; 12217 resolved to local targets, while 20869 stayed external or unresolved.

Among the most connected modules, mitmproxy/proxy/commands.py (853 incoming, 0 outgoing calls) and mitmproxy/proxy/events.py (514 incoming, 0 outgoing) are labeled leaf/data-boundary candidates: code that other modules call heavily while it calls little itself.

mitmproxy/proxy/layers/http/__init__.py is labeled a service/core candidate with 416 incoming and 152 outgoing calls.

Test support carries the highest connectivity: test/mitmproxy/proxy/tutils.py (1118 incoming), mitmproxy/test/tflow.py (553) and mitmproxy/test/taddons.py (317) are labeled service/core candidates, indicating how deeply the test harness is woven in.

In the web frontend, web/src/js/filt/filt.js shows 193 incoming and 193 outgoing static calls.

Role labels are the analyzer's candidates derived from call degree and entrypoint membership, not verified architecture.

All 44 dependency records in the packet come from web/package.json: 18 runtime dependencies — including react, react-dom, @reduxjs/toolkit and CodeMirror libraries — and 26 development dependencies.

Declared web tooling includes jest with a jsdom environment, Testing Library packages, vite, TypeScript and ESLint.

Python-side dependencies are absent from the evidence: the analyzer parses only requirements-style manifests and did not read pyproject.toml dependency tables, even though pyproject.toml is one of two manifest files found.

The repository contains 194 test-like files; sample paths include test/mitmproxy/test_addonmanager.py and test/mitmproxy/test_connection.py.

The heaviest test files target the proxy layers: test_http.py and test_http2.py are labeled service/core candidates and contain tests such as test_http_proxy, test_https_proxy, test_redirect and test_simple.

Dependency and test figures are inventory counts only; nothing was installed and no test was run for this asset.

This order follows the packet's importance classifications and entrypoint flags.

1. README.md, pyproject.toml and LICENSE — the analyzer-classified project-level files, for self-description, packaging and license terms.
2. mitmproxy/tools/main.py — the heuristic entrypoint — and mitmproxy/version.py, whose __main__ guard prints VERSION.
3. mitmproxy/proxy/commands.py, then mitmproxy/proxy/events.py, then mitmproxy/proxy/layers/http/__init__.py; roles mark commands.py and events.py as heavily-called leaf/data-boundary candidates and the HTTP layer as a service/core candidate.
4. test/mitmproxy/proxy/layers/http/test_http.py — tests like test_http_proxy and test_https_proxy as concrete behavior examples.
5. web/src/js/filt/filt.js, entering at peg$parse — the frontend's filter-expression parser.

The evidence is static only: reflection, runtime dependency injection, dynamic imports, monkey-patching, generated code, framework runtime wiring and dynamic dispatch are not resolved, so add-on or plugin loading through such mechanisms cannot be traced.

Install, run and build inference is partial, and installation commands are not verified.

pyproject.toml dependency tables were not parsed, so Python requirements are unknown from this packet.

README claim extraction is line-based and may capture code lines instead of prose, so README claims would be author_claimed at best; no README text is used in this asset.

Bounded analysis inventoried but did not parse four files — including minified bundles under mitmproxy/tools/web/static/ and large assets under docs/src/assets/ — and relation extraction is capped at 2500 per file and 150000 per repository.

Of 33086 static relations, 20869 remain external or unresolved, and all six execution paths listed in the packet end at unresolved boundaries.

What mitmproxy/tools/main.py launches at startup, and how add-ons are wired at runtime, is not established by this packet.

• mitmproxy/proxy/commands.py defines the command vocabulary as small classes: Command, RequestWakeup, ConnectionCommand, SendData, OpenConnection, CloseConnection, StartHook and Log.
• mitmproxy/proxy/events.py defines the event side: Event, Start, ConnectionEvent, DataReceived, ConnectionClosed, CommandCompleted, OpenConnectionCompleted, HookCompleted, MessageInjected and Wakeup.
• mitmproxy/proxy/layers/http/__init__.py contains the large HttpStream (lines 159-918) and HttpLayer (lines 921-1188) classes, plus HttpClient and commands like GetHttpConnection and SendHttp.
• mitmproxy/test/tflow.py provides flow factory functions: tflow, ttcpflow, tudpflow, twebsocketflow, tdnsflow, tclient_conn and tserver_conn.
• web/src/js/filt/filt.js exposes peg$parse and peg$-prefixed helpers and carries 193 incoming and 193 outgoing static calls.