EVEMISSTechnology

Repository guide · architecture · v2

microsoft / markitdown · Architecture

A Python repository of four packages under packages/: the core markitdown library with format converters, plus MCP, OCR and sample-plugin packages. Static call degree points to _markitdown.py as the core hub. The listed execution paths cover only the MCP entry, and they stop quickly at unresolved external calls.

Original repository
microsoft/markitdown
License
MIT · open-source license
Analyzed revision · last verified
ed178952a6672abdfd35b5f9e76a80b6cefc086e ·

microsoft/markitdown architecture: how it is structured

Terms used on this page
Entrypoint record
A file the analyzer marks as a place where execution can start. When it carries a __main__ guard excerpt, the file contains an if __name__ == "__main__": block and the excerpt shows what that block calls; without an excerpt, the file was flagged by its name only.
Bounded static execution path
A call chain reconstructed from the source code without running it, stopped after a fixed number of steps. It shows how far the code can be followed on paper, not what happens at run time.
Unresolved boundary
Where a static path stops because the next call goes into an external library or cannot be resolved without running the code. It marks the edge of this analysis, not a defect in the repository.
Static relations
Calls and imports found in the source. "External or unresolved" relations point outside the analyzed files.
Module role
The analyzer's label for a file, inferred from how many calls go in and out (for example core, entry/orchestration, leaf). It describes a position in the call graph, not the authors' design.
Test-like files
Files whose names or locations look like tests. This analysis counts them; it does not run them.
Observed · inferred · author-claimed · unresolved
How each statement is supported: read directly from the analyzed files; derived by the analyzer from them; stated by the repository's authors (metadata, README); or not established by this analysis.
Verified
Two uses on these pages. In an analyzer record ("verified provenance", "a verified entrypoint") it means the record was read directly from the analyzed files, which these guides call observed; for an entrypoint, the __main__ guard text is present. Since the analyzer fix of 2026-10-04, a file that only has an entrypoint-like name such as cli.py or main.py is recorded as inferred; guides analyzed before that still call such a file verified, and it is still only a guess about how the file is used. It does not mean the code was run or tested. "Last verified" is the date the guide last passed the lab's checks against the analysis record of the stated revision; it is not a review of the repository itself.

Shape at a glance

The analyzer inventoried 197 files: 181 under packages/, 10 at the root, 5 in .github and 1 in .devcontainer. It counts 112 of them as test-like. The packet carries no subsystem or module records, so the parts below are read from manifest and file paths.

  • packages/markitdown is the core library. Its src/markitdown tree holds _markitdown.py, a converters/ package and converter_utils/ helpers.
  • packages/markitdown-mcp has its own __main__.py.
  • packages/markitdown-ocr holds _plugin.py and _ocr_service.py.
  • packages/markitdown-sample-plugin has a test file with a __main__ guard.

Each of these four directories has its own pyproject.toml. The repository metadata describes the project as a Python tool for converting files and office documents to Markdown.

Entry points and control flow

The analyzer lists 24 __main__ guard records across 22 files. Only two are package modules: packages/markitdown/src/markitdown/__main__.py and packages/markitdown-mcp/src/markitdown_mcp/__main__.py. The rest sit under tests/, including two fixture generators. Both package guards simply call main().

All ten listed execution paths start at the MCP package's __main__.py. None is truncated, none has a cycle, and each ends with the terminal reason unresolved_boundary. Eight paths step through main() first and stop at argparse.ArgumentParser, parser.add_argument, parser.parse_args, parser.error or sys.exit. The other two stop at module level on logging.getLogger and MCPServer.

The reconstruction counts 155 bounded paths, but only ten are in the packet. None of those ten starts at the core package's __main__.py, so the core command-line flow is not shown. The analyzer's summary picks the MCP __main__.py as the main starting place; that is an analyzer judgement, not a runtime observation.

Core modules and their inferred roles

The roles below are inferred by the analyzer from resolved cross-module call counts and entrypoint membership. They do not come from reading the intent of the code.

  • _markitdown.py is the clearest hub, with 33 outgoing and 4 incoming calls; it is tagged as a service/core candidate.
  • Heavily called leaf modules: _base_converter.py (21 incoming), converters/__init__.py (20), _exceptions.py (19) and _stream_info.py (14).
  • converter_utils/docx/math/omml.py makes 25 outgoing calls and latex_dict.py receives 25. The matching numbers suggest, but do not prove, a caller/lookup pair.
  • The format converters for xlsx, pptx, docx, pdf, audio, epub and Outlook msg have zero resolved incoming calls and are tagged as orchestration candidates. They are probably invoked through dispatch the analyzer does not resolve.
  • _html_converter.py (6 in, 4 out), _markdownify.py (6 in) and converter_utils/_image.py (3 in) are smaller shared nodes.
  • markitdown/__main__.py is the entry/orchestration candidate. In the OCR package, _plugin.py has 5 outgoing calls and _ocr_service.py has 4 incoming.

Where static paths stop

Every listed path stops at an external-or-unresolved target: standard-library logging, argparse parser objects, sys.exit, or MCPServer. No listed path reaches into the core markitdown package.

Across the whole repository, 5,812 of 6,816 static relations are external or unresolved, and only 1,004 resolve locally.

MCPServer is unresolved. The markitdown-mcp package declares mcp as a runtime dependency, which plausibly supplies it, but the packet does not show the import.

Plugin loading is not visible. The OCR package has a _plugin.py module, but the packet does not establish how the core package finds and loads it at runtime. Dynamic imports are outside the analyzer's scope.

Dependencies between parts

The manifest records show which packages build on the core package:

  • markitdown-mcp, markitdown-ocr and markitdown-sample-plugin each declare a runtime dependency on markitdown. The first two constrain it to >=0.1.9,<0.2.0.
  • The core package's runtime list is short: beautifulsoup4, requests, certifi, markdownify, magika, charset-normalizer and defusedxml.
  • Format libraries are optional in the core manifest: python-pptx, mammoth, pandas, openpyxl, xlrd, lxml, pdfminer.six, pdfplumber, olefile, pydub, SpeechRecognition, youtube-transcript-api and Azure packages. Several of these names appear in more than one record.
  • markitdown-ocr requires pdfminer.six, pdfplumber, PyMuPDF, mammoth, python-docx, python-pptx, pandas, openpyxl and Pillow at runtime, with openai optional.
  • markitdown-mcp adds mcp, and the sample plugin adds striprtf.

Statically, the analyzer extracted 925 import relations and 5,891 call relations. Dependency records come only from requirements files, package.json and pyproject.toml. Files such as setup.py, setup.cfg, Pipfile and lock files are not parsed.

What static analysis cannot show

  • Runtime wiring: the analyzer does not resolve reflection, dependency injection, dynamic imports, monkey-patching, generated code, framework wiring or dynamic dispatch.
  • Configuration and commands: install, run and build inference is partial, and no installation command is verified. None is given here.
  • Coverage bounds: files over 400 kB, minified bundles and vendored directories are inventoried but not parsed. Relation extraction is capped per file and per repository.
  • Tests as behaviour: the analyzer counts 112 test-like files, which suggests at least some expected behaviour is encoded in tests. Static analysis reads them only as code and does not report whether they pass.

Reading order for the architecture

  1. packages/markitdown/src/markitdown/__main__.py, the core entry candidate.
  2. _markitdown.py, the highest-degree hub.
  3. _base_converter.py and _stream_info.py, two heavily called leaf modules.
  4. packages/markitdown-mcp/src/markitdown_mcp/__main__.py, then the OCR package's _plugin.py and _ocr_service.py, to see how the outer packages sit on top of the core.

What this analysis could not establish

The writing model's own notes on the analysis record. Identifiers such as lim_3, exec_* or claim_… name records of that analysis; the claims table cites the same records.

  • The packet lists only 10 of the 155 bounded execution paths the reconstruction reports, and all ten start at the MCP __main__.py; flows from the core CLI and the test entrypoints are not shown.
  • One of the analyzer's teaching claims states that no bounded static execution path is available, which conflicts with the ten listed execution-path records; this asset relies on those records.
  • The subsystems and modules lists in the packet are empty, so package grouping is read from paths rather than from analyzer-detected subsystems.
  • The packet's static core-flow, boundary and resolved-relation sample summaries carry no citable IDs, so details such as main calling create_starlette_app, or the OCR __init__.py importing register_converters, are not used as claims.
  • How many resolved relations cross package boundaries (for example from markitdown-ocr into markitdown) is not established; only repository-wide totals are given.
  • Many optional dependency names in packages/markitdown/pyproject.toml appear in duplicate records with the same line numbers; which optional groups they belong to is not established.
Claims and evidence — 36 claims, 36 supported by an independent verifier

Every substantive statement above is a claim bound to grounding IDs of the analyzed revision. Global grounding IDs are namespaced by the analysis run.

Claim Epistemic status Verifier Grounding (global IDs)
c1 The analyzer reports 197 files: 181 under packages/, 10 at the root, 5 in .github and 1 in .devcontainer, with 112 test-like files. inferred supported analysis_5d9c9ae9a129bff5:summary_repository
c2 Dependency records come from four pyproject.toml manifests, located in packages/markitdown, packages/markitdown-mcp, packages/markitdown-ocr and packages/markitdown-sample-plugin. observed supported analysis_5d9c9ae9a129bff5:dep_1, analysis_5d9c9ae9a129bff5:dep_3, analysis_5d9c9ae9a129bff5:dep_14, analysis_5d9c9ae9a129bff5:dep_16
c3 The packet carries no subsystem or module records, so any grouping by package is read from manifest and file paths; analyzer-detected subsystems are not established. unresolved supported analysis_5d9c9ae9a129bff5:dep_1, analysis_5d9c9ae9a129bff5:dep_3, analysis_5d9c9ae9a129bff5:dep_14, analysis_5d9c9ae9a129bff5:dep_16
c4 Module-role records place _markitdown.py, a converters/ package and converter_utils/ helpers inside packages/markitdown/src/markitdown. inferred supported analysis_5d9c9ae9a129bff5:role_13, analysis_5d9c9ae9a129bff5:role_22, analysis_5d9c9ae9a129bff5:role_20, analysis_5d9c9ae9a129bff5:role_16
c5 markitdown-mcp has its own __main__.py, markitdown-ocr holds _plugin.py and _ocr_service.py, and markitdown-sample-plugin has a test file with a __main__ guard. inferred supported analysis_5d9c9ae9a129bff5:py_entry_2f852a8015d4, analysis_5d9c9ae9a129bff5:role_6, analysis_5d9c9ae9a129bff5:role_4, analysis_5d9c9ae9a129bff5:py_entry_a63fdf323f3b
c6 The repository metadata describes the project as a Python tool for converting files and office documents to Markdown. author_claimed supported analysis_5d9c9ae9a129bff5:meta_description
c7 There are 24 __main__ guard records in 22 files. Two files are package modules (markitdown/__main__.py and markitdown_mcp/__main__.py); the others are under tests/, including two fixture generators in tests/test_files/. observed supported analysis_5d9c9ae9a129bff5:py_entry_2f852a8015d4, analysis_5d9c9ae9a129bff5:py_entry_1fa8ac31a8f1, analysis_5d9c9ae9a129bff5:py_entry_a63fdf323f3b, analysis_5d9c9ae9a129bff5:py_entry_d19b256901ab, analysis_5d9c9ae9a129bff5:py_entry_f44307e3b0be, analysis_5d9c9ae9a129bff5:py_entry_007b88c947c9, analysis_5d9c9ae9a129bff5:py_entry_48d5677c0b8c, analysis_5d9c9ae9a129bff5:py_entry_6da5faf654d3, analysis_5d9c9ae9a129bff5:py_entry_e1644548438f, analysis_5d9c9ae9a129bff5:py_entry_fd2581a2a85a, analysis_5d9c9ae9a129bff5:py_entry_157267349a98, analysis_5d9c9ae9a129bff5:py_entry_8a3faafff1be, analysis_5d9c9ae9a129bff5:py_entry_c1e9a0696ede, analysis_5d9c9ae9a129bff5:py_entry_4001ed8b5544, analysis_5d9c9ae9a129bff5:py_entry_2eddfb03d1cb, analysis_5d9c9ae9a129bff5:py_entry_791d98438517, analysis_5d9c9ae9a129bff5:py_entry_3c032b18438d, analysis_5d9c9ae9a129bff5:py_entry_32796e5c789a, analysis_5d9c9ae9a129bff5:py_entry_d48046c8aa24, analysis_5d9c9ae9a129bff5:py_entry_f19b18e9138b, analysis_5d9c9ae9a129bff5:py_entry_de1243d2bd26, analysis_5d9c9ae9a129bff5:py_entry_fc521ad126e1, analysis_5d9c9ae9a129bff5:py_entry_1f6c94e0f30f, analysis_5d9c9ae9a129bff5:py_entry_98eaed3ae984
c8 Both package __main__ guards consist of a call to main(). observed supported analysis_5d9c9ae9a129bff5:py_entry_2f852a8015d4, analysis_5d9c9ae9a129bff5:py_entry_d19b256901ab
c9 All ten listed execution paths start at markitdown_mcp/__main__.py. None is truncated, none has a cycle, and each ends with terminal reason unresolved_boundary. inferred supported analysis_5d9c9ae9a129bff5:exec_67998e701fae, analysis_5d9c9ae9a129bff5:exec_b68e1f5a7c8a, analysis_5d9c9ae9a129bff5:exec_11e5ff5e359f, analysis_5d9c9ae9a129bff5:exec_51ee1388edd7, analysis_5d9c9ae9a129bff5:exec_b64608cd49a8, analysis_5d9c9ae9a129bff5:exec_5be36f4ab619, analysis_5d9c9ae9a129bff5:exec_a37ea1d8706f, analysis_5d9c9ae9a129bff5:exec_763ce56ab606, analysis_5d9c9ae9a129bff5:exec_b6c46e3ecba7, analysis_5d9c9ae9a129bff5:exec_a46c678eda14
c10 Eight of the ten paths pass through local main() before stopping at argparse.ArgumentParser, parser.add_argument, parser.parse_args, parser.error or sys.exit. Two stop at module level on logging.getLogger and MCPServer. inferred supported analysis_5d9c9ae9a129bff5:exec_67998e701fae, analysis_5d9c9ae9a129bff5:exec_b68e1f5a7c8a, analysis_5d9c9ae9a129bff5:exec_11e5ff5e359f, analysis_5d9c9ae9a129bff5:exec_51ee1388edd7, analysis_5d9c9ae9a129bff5:exec_b64608cd49a8, analysis_5d9c9ae9a129bff5:exec_5be36f4ab619, analysis_5d9c9ae9a129bff5:exec_a37ea1d8706f, analysis_5d9c9ae9a129bff5:exec_763ce56ab606, analysis_5d9c9ae9a129bff5:exec_b6c46e3ecba7, analysis_5d9c9ae9a129bff5:exec_a46c678eda14
c11 The reconstruction reports 155 bounded paths, but only ten are listed. None of the ten starts at packages/markitdown/src/markitdown/__main__.py, so the core CLI flow is not shown in this packet. inferred supported analysis_5d9c9ae9a129bff5:architecture_reconstruction, analysis_5d9c9ae9a129bff5:exec_67998e701fae, analysis_5d9c9ae9a129bff5:exec_b68e1f5a7c8a, analysis_5d9c9ae9a129bff5:exec_11e5ff5e359f, analysis_5d9c9ae9a129bff5:exec_51ee1388edd7, analysis_5d9c9ae9a129bff5:exec_b64608cd49a8, analysis_5d9c9ae9a129bff5:exec_5be36f4ab619, analysis_5d9c9ae9a129bff5:exec_a37ea1d8706f, analysis_5d9c9ae9a129bff5:exec_763ce56ab606, analysis_5d9c9ae9a129bff5:exec_b6c46e3ecba7, analysis_5d9c9ae9a129bff5:exec_a46c678eda14
c12 The analyzer's summary names markitdown_mcp/__main__.py as the main starting place; this is an analyzer judgement rather than a runtime observation. inferred supported analysis_5d9c9ae9a129bff5:summary_repository
c13 All listed module roles are inferred from static resolved cross-module call degree and entrypoint membership, not from the intent of the code. inferred supported analysis_5d9c9ae9a129bff5:role_13, analysis_5d9c9ae9a129bff5:role_20, analysis_5d9c9ae9a129bff5:role_19, analysis_5d9c9ae9a129bff5:role_11, analysis_5d9c9ae9a129bff5:role_22, analysis_5d9c9ae9a129bff5:role_12, analysis_5d9c9ae9a129bff5:role_14, analysis_5d9c9ae9a129bff5:role_31, analysis_5d9c9ae9a129bff5:role_43, analysis_5d9c9ae9a129bff5:role_39, analysis_5d9c9ae9a129bff5:role_35, analysis_5d9c9ae9a129bff5:role_6, analysis_5d9c9ae9a129bff5:role_4, analysis_5d9c9ae9a129bff5:role_10, analysis_5d9c9ae9a129bff5:role_28, analysis_5d9c9ae9a129bff5:role_16, analysis_5d9c9ae9a129bff5:role_23, analysis_5d9c9ae9a129bff5:role_29, analysis_5d9c9ae9a129bff5:role_36, analysis_5d9c9ae9a129bff5:role_37
c14 _markitdown.py has 33 outgoing and 4 incoming resolved calls and is tagged as a service/core candidate, which makes it the clearest hub among the listed roles. inferred supported analysis_5d9c9ae9a129bff5:role_13
c15 _base_converter.py (21 incoming), converters/__init__.py (20), _exceptions.py (19) and _stream_info.py (14) have no outgoing calls and are tagged as leaf/data-boundary candidates. inferred supported analysis_5d9c9ae9a129bff5:role_11, analysis_5d9c9ae9a129bff5:role_22, analysis_5d9c9ae9a129bff5:role_12, analysis_5d9c9ae9a129bff5:role_14
c16 omml.py makes 25 outgoing calls and latex_dict.py receives 25 incoming calls. The matching counts suggest, but do not establish, that omml.py is the main caller of latex_dict.py. inferred supported analysis_5d9c9ae9a129bff5:role_20, analysis_5d9c9ae9a129bff5:role_19
c17 The xlsx, pptx, docx, pdf, audio, epub and Outlook msg converters have zero resolved incoming calls and are tagged as orchestration candidates. They are probably invoked through dispatch the analyzer does not resolve. inferred supported analysis_5d9c9ae9a129bff5:role_43, analysis_5d9c9ae9a129bff5:role_39, analysis_5d9c9ae9a129bff5:role_28, analysis_5d9c9ae9a129bff5:role_37, analysis_5d9c9ae9a129bff5:role_23, analysis_5d9c9ae9a129bff5:role_29, analysis_5d9c9ae9a129bff5:role_36, analysis_5d9c9ae9a129bff5:lim_1
c18 _html_converter.py (6 incoming, 4 outgoing), _markdownify.py (6 incoming) and converter_utils/_image.py (3 incoming) are smaller shared nodes in the call graph. inferred supported analysis_5d9c9ae9a129bff5:role_31, analysis_5d9c9ae9a129bff5:role_35, analysis_5d9c9ae9a129bff5:role_16
c19 markitdown/__main__.py is an entry/orchestration candidate with 4 outgoing calls. In the OCR package, _plugin.py has 5 outgoing calls and _ocr_service.py has 4 incoming calls. inferred supported analysis_5d9c9ae9a129bff5:role_10, analysis_5d9c9ae9a129bff5:role_6, analysis_5d9c9ae9a129bff5:role_4
c20 Every listed path stops at an external-or-unresolved target (logging, argparse parser objects, sys.exit or MCPServer). No listed path reaches into the core markitdown package. inferred supported analysis_5d9c9ae9a129bff5:exec_67998e701fae, analysis_5d9c9ae9a129bff5:exec_b68e1f5a7c8a, analysis_5d9c9ae9a129bff5:exec_11e5ff5e359f, analysis_5d9c9ae9a129bff5:exec_51ee1388edd7, analysis_5d9c9ae9a129bff5:exec_b64608cd49a8, analysis_5d9c9ae9a129bff5:exec_5be36f4ab619, analysis_5d9c9ae9a129bff5:exec_a37ea1d8706f, analysis_5d9c9ae9a129bff5:exec_763ce56ab606, analysis_5d9c9ae9a129bff5:exec_b6c46e3ecba7, analysis_5d9c9ae9a129bff5:exec_a46c678eda14
c21 Of 6,816 static relations, 5,812 are external or unresolved and 1,004 resolve locally. observed supported analysis_5d9c9ae9a129bff5:relation_counts
c22 MCPServer is an unresolved target. markitdown-mcp declares mcp as a runtime dependency, which plausibly supplies it, but the packet does not show the import. inferred supported analysis_5d9c9ae9a129bff5:exec_b68e1f5a7c8a, analysis_5d9c9ae9a129bff5:dep_1
c23 How the core package discovers and loads the OCR package's _plugin.py at runtime is not established, because the analyzer does not resolve dynamic imports. unresolved supported analysis_5d9c9ae9a129bff5:role_6, analysis_5d9c9ae9a129bff5:lim_1
c24 markitdown-mcp, markitdown-ocr and markitdown-sample-plugin each declare a runtime dependency on markitdown. The first two use the constraint >=0.1.9,<0.2.0. observed supported analysis_5d9c9ae9a129bff5:dep_2, analysis_5d9c9ae9a129bff5:dep_3, analysis_5d9c9ae9a129bff5:dep_14
c25 The core markitdown manifest lists beautifulsoup4, requests, certifi, markdownify, magika, charset-normalizer and defusedxml as runtime dependencies. observed supported analysis_5d9c9ae9a129bff5:dep_16, analysis_5d9c9ae9a129bff5:dep_17, analysis_5d9c9ae9a129bff5:dep_18, analysis_5d9c9ae9a129bff5:dep_19, analysis_5d9c9ae9a129bff5:dep_20, analysis_5d9c9ae9a129bff5:dep_21, analysis_5d9c9ae9a129bff5:dep_22
c26 Format libraries such as python-pptx, mammoth, pandas, openpyxl, xlrd, lxml, pdfminer.six, pdfplumber, olefile, pydub, SpeechRecognition, youtube-transcript-api and Azure packages are optional in the core manifest. Several names recur across records. observed supported analysis_5d9c9ae9a129bff5:dep_23, analysis_5d9c9ae9a129bff5:dep_24, analysis_5d9c9ae9a129bff5:dep_25, analysis_5d9c9ae9a129bff5:dep_26, analysis_5d9c9ae9a129bff5:dep_27, analysis_5d9c9ae9a129bff5:dep_28, analysis_5d9c9ae9a129bff5:dep_29, analysis_5d9c9ae9a129bff5:dep_30, analysis_5d9c9ae9a129bff5:dep_31, analysis_5d9c9ae9a129bff5:dep_32, analysis_5d9c9ae9a129bff5:dep_33, analysis_5d9c9ae9a129bff5:dep_34, analysis_5d9c9ae9a129bff5:dep_35, analysis_5d9c9ae9a129bff5:dep_36, analysis_5d9c9ae9a129bff5:dep_37, analysis_5d9c9ae9a129bff5:dep_38, analysis_5d9c9ae9a129bff5:dep_39, analysis_5d9c9ae9a129bff5:dep_40, analysis_5d9c9ae9a129bff5:dep_41, analysis_5d9c9ae9a129bff5:dep_42, analysis_5d9c9ae9a129bff5:dep_43, analysis_5d9c9ae9a129bff5:dep_44, analysis_5d9c9ae9a129bff5:dep_45, analysis_5d9c9ae9a129bff5:dep_46, analysis_5d9c9ae9a129bff5:dep_47, analysis_5d9c9ae9a129bff5:dep_48, analysis_5d9c9ae9a129bff5:dep_49, analysis_5d9c9ae9a129bff5:dep_50, analysis_5d9c9ae9a129bff5:dep_51, analysis_5d9c9ae9a129bff5:dep_52, analysis_5d9c9ae9a129bff5:dep_53, analysis_5d9c9ae9a129bff5:dep_54
c27 markitdown-ocr lists pdfminer.six, pdfplumber, PyMuPDF, mammoth, python-docx, python-pptx, pandas, openpyxl and Pillow as runtime dependencies, and openai as optional. observed supported analysis_5d9c9ae9a129bff5:dep_4, analysis_5d9c9ae9a129bff5:dep_5, analysis_5d9c9ae9a129bff5:dep_6, analysis_5d9c9ae9a129bff5:dep_7, analysis_5d9c9ae9a129bff5:dep_8, analysis_5d9c9ae9a129bff5:dep_9, analysis_5d9c9ae9a129bff5:dep_10, analysis_5d9c9ae9a129bff5:dep_11, analysis_5d9c9ae9a129bff5:dep_12, analysis_5d9c9ae9a129bff5:dep_13
c28 markitdown-mcp adds mcp as a runtime dependency, and markitdown-sample-plugin adds striprtf. observed supported analysis_5d9c9ae9a129bff5:dep_1, analysis_5d9c9ae9a129bff5:dep_15
c29 The analyzer extracted 925 import relations and 5,891 call relations. observed supported analysis_5d9c9ae9a129bff5:relation_counts
c30 Dependency records come only from requirements files, package.json and pyproject.toml. setup.py, setup.cfg, Pipfile and lock files are not parsed. observed supported analysis_5d9c9ae9a129bff5:lim_3a
c31 The analyzer does not resolve reflection, runtime dependency injection, dynamic imports, monkey-patching, generated code, framework runtime wiring or dynamic dispatch. observed supported analysis_5d9c9ae9a129bff5:lim_1
c32 Install, run and build inference is partial, and installation commands are not verified. observed supported analysis_5d9c9ae9a129bff5:lim_2
c33 Files over 400 kB, minified bundles and vendored directories are inventoried but not parsed. Relation extraction is capped at 2500 per file and 150000 per repository. observed supported analysis_5d9c9ae9a129bff5:lim_6
c34 The analyzer counts 112 test-like files, which suggests at least some expected behaviour is encoded in tests; static analysis reads them only as code and does not report whether they pass. inferred supported analysis_5d9c9ae9a129bff5:summary_repository, analysis_5d9c9ae9a129bff5:lim_1
c35 A suggested start is the core entry candidate markitdown/__main__.py, then the hub _markitdown.py, then the heavily called leaf modules _base_converter.py and _stream_info.py. inferred supported analysis_5d9c9ae9a129bff5:py_entry_d19b256901ab, analysis_5d9c9ae9a129bff5:role_10, analysis_5d9c9ae9a129bff5:role_13, analysis_5d9c9ae9a129bff5:role_11, analysis_5d9c9ae9a129bff5:role_14
c36 After the core modules, reading markitdown_mcp/__main__.py and the OCR package's _plugin.py and _ocr_service.py shows how the outer packages sit on top of the core. inferred supported analysis_5d9c9ae9a129bff5:py_entry_2f852a8015d4, analysis_5d9c9ae9a129bff5:role_6, analysis_5d9c9ae9a129bff5:role_4, analysis_5d9c9ae9a129bff5:dep_2, analysis_5d9c9ae9a129bff5:dep_3

Sources, rights and disclosure · attribution-license-templates/v0.1

Rights notice. Original repository hosted on GitHub. Repository source code, documentation, names, media, and related project materials remain subject to the rights of their respective authors, contributors, and other rights holders and to applicable repository license terms.

Platform notice. GitHub is the source hosting platform for the linked repository. GitHub and related marks are trademarks of GitHub, Inc. EVEMISS Technology is not affiliated with or endorsed by GitHub unless explicitly stated otherwise.

How this page is produced. This page was produced using revision-aware repository analysis and AI-assisted editorial tooling. Technical claims are tied to the analyzed repository revision and may be revalidated when the source repository changes.

AI-assisted analysis. Reviewed by EVEMISS Technology through human–AI collaborative review. · Report a rights concern · Back to the overview