mitmproxy / mitmproxy · Architecture

The analyzer treats four top-level directories as subsystems: docs, mitmproxy, test and web. The repository holds 1292 analyzed files - mitmproxy 285, test 427, web 286, docs 166, examples 73, release 33, .github 9, plus 13 root-level entries. The mitmproxy directory is the Python package; module paths show a proxy/layers area with an HTTP layer, and dns, tls, websocket, quic, http2 and http3 layers exercised under test/. web/ is a JavaScript frontend: its package.json defines a start script running vite and records React, Redux and CodeMirror runtime dependencies. Around the code: docs/ contains a CLI-recording script, examples/ holds contrib wrappers such as mitmproxywrapper.py, release/ carries build/deploy/release scripts, and test/ contributes 194 test-like files. GitHub metadata lists Python as the primary language, with topics including http, proxy, tls and websocket.

The analyzer detected 28 entrypoints and 245 bounded execution paths. Recorded __main__ guards cluster in release scripts (release/build.py, release/deploy.py, release/release.py), in five generators under web/gen/, in test helper tools, and in library modules like version.py, proxy/server.py and platform/windows.py; the version.py guard prints VERSION. mitmproxy/tools/main.py and mitmproxy/tools/web/app.py are flagged as likely executable entrypoints by filename heuristic; web/package.json's start script runs vite. The analyzer's summary names mitmproxy/version.py as the starting place (an inferred reading). Of the ten listed execution paths, the five from docs/scripts/clirecording/record.py:__main__ end after one step at CliDirector or a screenplays.record_* function, each with terminal_reason unresolved_boundary. Two listed paths from examples/contrib/mitmproxywrapper.py:__main__ end at Wrapper.ensure_superuser and Wrapper.main. One listed path stays local: mitmproxy/contentviews/_view_css.py:__main__ reaches ViewCSS in-module and stops as a leaf; two siblings end at the built-ins open and f.read. No listed path is truncated or cyclic; paths end because callees are external or unresolved, or at a leaf. The packet also reports one entrypoint path with no statically detected call steps, so its continuation is not established.

Role labels are candidates the analyzer derives from static resolved call degree and entrypoint membership - inferred from call counts, not confirmed behavior; all 20 role records share this evidence basis. Among production modules, mitmproxy/proxy/commands.py (853 incoming, 0 outgoing) and mitmproxy/proxy/events.py (514 incoming, 0 outgoing) are leaf/data-boundary candidates, and mitmproxy/proxy/layers/http/__init__.py (416 in, 152 out) is a service/core candidate. mitmproxy/http.py (217 in, 71 out), mitmproxy/contentviews/__init__.py (179 in, 12 out) and mitmproxy/tools/console/common.py (100 in, 84 out) are service/core candidates. Test support dominates incoming degree: test/mitmproxy/proxy/tutils.py (1118 in), mitmproxy/test/tflow.py (553), mitmproxy/test/taddons.py (317) and mitmproxy/test/tutils.py (254). On the web side, web/src/js/filt/filt.js balances 193 incoming and 193 outgoing; test_modes.py (252 outgoing) and test_dns.py (225 outgoing) are orchestration candidates with zero incoming calls.

Static paths stop where calls leave analyzable code. Of 33086 recorded relations, 12217 are local and 20869 external or unresolved - 28836 calls and 4250 imports overall. Listed boundaries are module-level targets outside parsed scope: CliDirector and the screenplays.record_* functions from docs/scripts/clirecording/record.py, and Wrapper.ensure_superuser / Wrapper.main from examples/contrib/mitmproxywrapper.py. Built-ins bound analysis too: open and f.read reached from mitmproxy/contentviews/_view_css.py; with 20869 unresolved edges, the listed boundaries are samples, not an exhaustive map. Paths end with terminal_reason unresolved_boundary when a callee cannot be resolved to parsed code; reflection, dynamic imports, monkey-patching, generated code, framework runtime wiring and dynamic dispatch are documented as unresolved. None of the ten listed paths terminates in plugin loading; dispatch-based mechanisms would appear only as unresolved edges.

All 44 dependency records come from web/package.json: 18 runtime records (react, react-dom, react-redux, @reduxjs/toolkit, codemirror with its language and theme packages, lodash, lucide-react, qrcode) and 26 dev records (vite, jest, typescript, eslint, testing-library packages, prettier and others). The Python side has no dependency records: the analyzer version used here (v0.10) parsed only requirements-style manifests, not pyproject.toml dependency tables, though pyproject.toml is a project-level important file. Quoted from the packet's resolved-relation summary sample (a prose list, not a citable record): mitmproxy/addonmanager.py imports mitmproxy/exceptions.py, mitmproxy/flow.py and mitmproxy/hooks.py, and AddonManager methods call hook classes (ConfigureHook, LoadHook, UpdateHook, DoneHook) and helpers such as traverse and safecall. What the analyzer could not resolve: 20869 external-or-unresolved edges and no dependency records for Python packages, so Python third-party dependencies are not established here.

Runtime wiring is outside this analysis: reflection, runtime dependency injection, dynamic imports, monkey-patching, generated code, framework runtime wiring and dynamic dispatch are not resolved. Generated code is present: five web/gen guards write frontend artifacts via asyncio.run(make()), and minified bundles plus oversized or vendored files are inventoried but not parsed. Four files fall in that unparsed bucket; the packet marks this unresolved. Runtime flow of the proxy itself is not established: one packet claim says no bounded static execution path is available for runtime flow, even though the reconstruction reports 245 bounded paths. The packet counts 194 test-like files, but which behaviors they establish at runtime is not resolved by static data. Install/run/build inference is partial and installation commands are unverified, so this packet supports no run instructions.

Read README.md, pyproject.toml and LICENSE first - all flagged as project-level important files. The packet's grounded sequence: manifests and important symbols, then the bounded execution paths, then the unresolved boundaries before changing code. For modification work, the analyzer suggests beginning at the detected entrypoint mitmproxy/tools/main.py and checking downstream effects manually.