Repository 指南 · 概覽 · v2
microsoft / markitdown
“Python tool for converting files and office documents to Markdown.” — 作者自述
- Data Processing
- Python
- MIT · 開源授權
- 原始 repository
- microsoft/markitdown
- 來源平台
- GitHub
- 擁有者 / 組織
- microsoft
- 授權
- MIT · 開源授權
- 分析的版本
- ed178952a6672abdfd35b5f9e76a80b6cefc086e
- 最後驗證
2026-11-15 檢查過原始專案:預設分支仍在分析的版本。
本頁中文由負責的 AI 編輯依英文正式版本 v2 翻譯;程式碼名稱、路徑、行號與數字都經確定性檢查,與英文版一致。陳述與依據表保留英文原文,因為那是獨立驗證者核對過的紀錄。看英文原文
microsoft/markitdown repository 概覽
本頁用語說明
- Entrypoint record(進入點記錄)
- 分析器標記為「程式可能從這裡開始執行」的檔案。附有 __main__ guard 摘錄時,表示檔案裡有 if __name__ == "__main__": 區塊,摘錄顯示它呼叫了什麼;沒有摘錄時,只是依檔名判斷。
- Bounded static execution path(有界靜態執行路徑)
- 不執行程式、直接從原始碼重建出的呼叫鏈,走到固定步數就停。它說明在紙面上能追到多遠,不代表實際執行時會發生什麼。
- Unresolved boundary(未解析邊界)
- 靜態路徑停下的地方:下一個呼叫進入外部函式庫,或不執行就無法確定。這是本次分析的邊界,不是 repository 的缺陷。
- Static relations(靜態關係)
- 在原始碼中找到的呼叫與 import。「external or unresolved」表示指向分析範圍以外。
- Module role(模組角色)
- 分析器依呼叫進出次數推論的檔案標籤(例如 core、entry/orchestration、leaf)。它描述的是在呼叫圖中的位置,不是作者的設計意圖。
- Test-like files(類測試檔案)
- 名稱或位置看起來像測試的檔案。本次分析只計數,不執行。
- Observed · inferred · author-claimed · unresolved
- 每句話的依據:直接讀自分析的檔案;由分析器從檔案推論;repository 作者自述(metadata、README);或本次分析無法確定。
- Verified(已驗證)
- 本頁有兩種用法。在分析器的記錄裡(「verified provenance」「verified entrypoint」),它表示這筆記錄是直接從分析的檔案讀到的,也就是本指南所說的 observed;以進入點來說,就是檔案裡確實有 __main__ guard 的文字。分析器在 2026-10-04 修正後,只有 cli.py、main.py 這類像進入點的檔名、沒有 guard 的檔案,會記為 inferred(推測);在那之前分析的指南仍把這類檔案標成 verified,它依然只是對檔案用途的推測。它不代表程式被執行或測試過。「最後驗證」是這份指南最後一次通過本實驗室檢查的日期,檢查對象是所標示版本的分析記錄,不是對 repository 本身的審查。
一個 Python monorepo,它的 GitHub 描述說它能把檔案和 Office 文件轉換成 Markdown。它包含四個套件:核心 `markitdown` 函式庫、一個 MCP server、一個 OCR 附加元件和一個範例 plugin。靜態呼叫度數指出 `_markitdown.py` 是核心樞紐。大多數關係都未解析,執行期行為也尚未確定。
這是什麼
根據它的 GitHub 描述,這是一個用來把檔案和 Office 文件轉換成 Markdown 的 Python 工具。平台 metadata 列出的主要語言是 Python,授權是 MIT。列出的主題包括 markdown、pdf、microsoft-office、openai、langchain 和 autogen。
從結構上看,這個 repository 是一個小型 monorepo。packages/ 底下有四個 pyproject.toml manifest,分別對應 markitdown、markitdown-mcp、markitdown-ocr 和 markitdown-sample-plugin。
平台上最新的 release 是 v0.1.9。markitdown-mcp 和 markitdown-ocr 都宣告了對 markitdown 的執行期依賴,版本範圍是 >=0.1.9,<0.2.0。
從套件名稱和進入點判斷,markitdown 看起來是核心的轉換函式庫。其他三個套件看起來分別是 MCP server 包裝層、OCR 附加元件和 plugin 範例。
如何啟動
有兩個 __main__ 守衛位於函式庫原始碼中,不是在測試裡:packages/markitdown/src/markitdown/__main__.py 和 packages/markitdown-mcp/src/markitdown_mcp/__main__.py。這兩個守衛都會呼叫 main() 函式。
偵測到的其他守衛大多位於測試模組和 fixture 產生器中。它們會把自己的檔案交給 pytest.main,或直接呼叫測試輔助函式或本地的 main。test_cli_vectors.py 和 test_module_vectors.py 中有些守衛只負責切換 import。
這份分析資料中的有界靜態路徑只涵蓋 MCP 進入點。在那裡,守衛呼叫 main,它會建立一個 argparse 解析器。追蹤到的路徑停在外部邊界,例如 argparse.ArgumentParser 和 parser.add_argument。
在模組層級,同一個檔案參照了 MCPServer 和 logging.getLogger,兩者都未解析。對於 MCPServer,靜態分析沒有解析出它的來源;它很可能來自 mcp 依賴。
分析資料中沒有核心 markitdown/__main__.py 的執行路徑。因此,命令列進入點如何抵達 MarkItDown 類別,在這裡尚未確定。
結構
根據分析器的摘要,197 個檔案中有 181 個位於 packages/ 底下。其餘位於根目錄(10)、.github(5)和 .devcontainer(1)。
依已解析的跨模組呼叫度數為模組排序,可以大致看出核心函式庫的樣貌:
markitdown/_markitdown.py的呼出最多(33 個,傳入呼叫 4 個)。它定義了龐大的MarkItDown類別(第 141-861 行)、ConverterRegistration類別和_load_plugins,因此很可能是協調樞紐。_base_converter.py(21 個呼入)、converters/__init__.py(20)、_exceptions.py(19)和_stream_info.py(14)沒有呼出。它們看起來是共用定義,例如DocumentConverter、DocumentConverterResult、StreamInfo和例外型別。converter_utils/docx/math/omml.py(25 個呼出)和latex_dict.py(25 個呼入)看起來構成一組,透過oMath2Latex把 Office 數學標記轉換成 LaTeX。- 像
_xlsx_converter.py和_pptx_converter.py這類格式轉換器,已解析的呼入為零。這符合轉換器是經由註冊並間接分派、不是直接以名稱呼叫的情況。
依賴與測試
依賴記錄來自四個 pyproject.toml 檔案:
markitdown:記錄到的執行期依賴包括beautifulsoup4、requests、certifi、markdownify、magika、charset-normalizer和defusedxml。選用依賴涵蓋特定格式和服務,包括python-pptx、mammoth、pandas、openpyxl、xlrd、lxml、pdfminer.six、pdfplumber、olefile、pydub、SpeechRecognition、youtube-transcript-api以及 Azure 套件。markitdown-mcp:mcp(>=2.1.1,<3.0.0)和markitdown。markitdown-ocr:markitdown加上 PDF、Office 和影像處理函式庫,以及選用的openai。markitdown-sample-plugin:markitdown和striprtf。
有幾筆選用依賴記錄重複了相同的名稱和行號,分析資料沒有說明原因。只有部分 manifest 類型會被解析,版本則照原文記錄。
分析器計算出 112 個測試或類似測試的檔案。抽樣清單中包含 fixture 文件,所以並不全是測試程式碼。各格式的測試模組(CSV、DOCX、EPUB、HTML、PDF、PPTX、XLSX、ZIP 等)都各自包含一個 pytest.main 守衛。
建議先讀什麼
這個建議順序結合了分析器標記為重要的檔案,以及連結最多的模組:
README.md和LICENSE,兩者都被標記為專案層級的重要檔案。packages/markitdown/src/markitdown/__main__.py,接著是_markitdown.py,重點放在MarkItDown、ConverterRegistration和_load_plugins。_base_converter.py、_stream_info.py和_exceptions.py,了解轉換器所依賴的共用型別。- 一個具體的轉換器,例如
converters/_html_converter.py(HtmlConverter),它同時有呼入和呼出。 packages/markitdown-mcp/src/markitdown_mcp/__main__.py搭配tests/test_stdio_protocols.py。接著閱讀packages/markitdown-sample-plugin/tests/test_sample_plugin.py,看看 plugin 是如何被測試執行的。
這份分析的限制
在 6,816 個靜態關係中,有 5,812 個是外部或未解析的,只有 1,004 個能在本地解析。大多數呼叫目標以文字保存,沒有連結到程式碼。
這份分析只做靜態分析,因此動態 import、執行期註冊和動態分派都沒有解析。核心包含 _load_plugins,而 OCR 和範例套件看起來是 plugin。因此,執行期實際啟用哪些轉換器,在這裡無法確定。
安裝、建置和執行方式的推論並不完整,也沒有任何指令經過驗證。因此本文不提供安裝或執行說明。
分析器本身的教學說明前後不一致。其中一則說不存在有界執行路徑,但分析資料中其實有好幾條。另一則把一個測試檔案列為起點。
在分析器的限制下,超過 400 kB 的檔案、minified bundle 和 vendored 目錄只會被列入清單,不會被解析。
任何進入點是否真的能執行,以及會產生什麼輸出,都尚未確定。
這次分析無法確定的事
這些是撰寫模型對分析記錄自己的說明。lim_3、exec_* 或 claim_… 這類識別碼指的是那次分析裡的記錄;陳述與依據表引用的也是同一批記錄。
- 分析器的一則教學陳述表示沒有可用的有界靜態執行路徑,但分析資料中含有執行路徑記錄,而且分析器回報了 155 條有界執行路徑。
- 分析器指出了不同的起點:它的 repository 摘要指向 MCP 的 __main__.py,而它的一則教學陳述則指向一個測試檔案(test_cli_vectors.py)。
- packages/markitdown/src/markitdown/__main__.py 的控制流程沒有被分析資料中的任何執行路徑涵蓋。
- packages/markitdown/pyproject.toml 中選用依賴 extras 的名稱不在分析資料中,而且有幾筆記錄重複。
- markitdown-ocr 和 markitdown-sample-plugin 在執行期如何被發現和註冊,尚未確定;只有檔案名稱和 import 關係暗示存在 plugin 機制。
- certifi 的版本限制(>=2026.10.19)和其他版本字串都照原文記錄,未經檢查。
陳述與依據 — 36 條陳述,36 條經獨立驗證者確認(英文原文)
上面每一句都是一條陳述,各自引用分析裡的依據編號。編號是這次分析內部的;表格列出每條陳述靠的是什麼、依據有多強。
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 GitHub description says the project is a Python tool for converting files and office documents to Markdown. | author_claimed | supported | analysis_5d9c9ae9a129bff5:meta_description |
| c2 Platform metadata lists Python as the primary language and MIT as the license, with topics including markdown, pdf, microsoft-office, openai, langchain and autogen. | observed | supported | analysis_5d9c9ae9a129bff5:meta_primary_language, analysis_5d9c9ae9a129bff5:meta_license, analysis_5d9c9ae9a129bff5:meta_topics |
| c3 The repository has four pyproject.toml manifests under packages/, for markitdown, markitdown-mcp, markitdown-ocr and markitdown-sample-plugin. | observed | supported | analysis_5d9c9ae9a129bff5:ev_manifest_1, analysis_5d9c9ae9a129bff5:dep_1, analysis_5d9c9ae9a129bff5:dep_3, analysis_5d9c9ae9a129bff5:dep_14, analysis_5d9c9ae9a129bff5:dep_16 |
| c4 The latest platform release is v0.1.9, and markitdown-mcp and markitdown-ocr both require markitdown >=0.1.9,<0.2.0 at runtime. | observed | supported | analysis_5d9c9ae9a129bff5:meta_latest_release, analysis_5d9c9ae9a129bff5:dep_2, analysis_5d9c9ae9a129bff5:dep_3 |
| c5 From package names and entrypoints, markitdown appears to be the core converter library, while the other packages look like an MCP server wrapper, an OCR add-on and a plugin example. | inferred | supported | analysis_5d9c9ae9a129bff5:important_6, analysis_5d9c9ae9a129bff5:important_3, analysis_5d9c9ae9a129bff5:important_5, analysis_5d9c9ae9a129bff5:dep_3 |
| c6 Non-test __main__ guards exist in packages/markitdown/src/markitdown/__main__.py and packages/markitdown-mcp/src/markitdown_mcp/__main__.py, and both call main(). | observed | supported | analysis_5d9c9ae9a129bff5:py_entry_d19b256901ab, analysis_5d9c9ae9a129bff5:py_entry_2f852a8015d4 |
| c7 Most other detected __main__ guards are in test modules and fixture generators and call pytest.main on their own file, test helpers or a local main; some guards in test_cli_vectors.py and test_module_vectors.py only switch imports. | observed | supported | analysis_5d9c9ae9a129bff5:py_entry_f44307e3b0be, analysis_5d9c9ae9a129bff5:py_entry_a63fdf323f3b, analysis_5d9c9ae9a129bff5:py_entry_157267349a98, analysis_5d9c9ae9a129bff5:py_entry_007b88c947c9, analysis_5d9c9ae9a129bff5:py_entry_791d98438517 |
| c8 Static paths from the MCP entry go from the guard to main, which reaches argparse.ArgumentParser and parser.add_argument, where the paths stop at unresolved boundaries. | inferred | supported | analysis_5d9c9ae9a129bff5:exec_11e5ff5e359f, analysis_5d9c9ae9a129bff5:exec_51ee1388edd7 |
| c9 The MCP __main__ module references MCPServer and logging.getLogger as unresolved external targets, so the server object probably comes from the mcp dependency. | inferred | supported | analysis_5d9c9ae9a129bff5:exec_b68e1f5a7c8a, analysis_5d9c9ae9a129bff5:exec_67998e701fae, analysis_5d9c9ae9a129bff5:dep_1 |
| c10 No execution path for packages/markitdown/src/markitdown/__main__.py is in the packet, so how it reaches the MarkItDown class is not established. | unresolved | supported | analysis_5d9c9ae9a129bff5:py_entry_d19b256901ab, analysis_5d9c9ae9a129bff5:py_class_54565613c36d |
| c11 The analyzer summary reports 197 files, 181 of them under packages/, with 10 at the root, 5 in .github and 1 in .devcontainer. | inferred | supported | analysis_5d9c9ae9a129bff5:summary_repository |
| c12 By static cross-module call degree, _markitdown.py (33 outgoing, 4 incoming) is the likely hub; it defines MarkItDown (lines 141-861), ConverterRegistration and _load_plugins. | inferred | supported | analysis_5d9c9ae9a129bff5:role_13, analysis_5d9c9ae9a129bff5:py_class_54565613c36d, analysis_5d9c9ae9a129bff5:py_class_a5c27a19fe56, analysis_5d9c9ae9a129bff5:py_func_575e8ec2d882 |
| c13 _base_converter.py, converters/__init__.py, _exceptions.py and _stream_info.py have many incoming and no outgoing resolved calls, and look like shared definitions such as DocumentConverter, DocumentConverterResult, StreamInfo and exception types. | inferred | supported | analysis_5d9c9ae9a129bff5:role_11, analysis_5d9c9ae9a129bff5:role_22, analysis_5d9c9ae9a129bff5:role_12, analysis_5d9c9ae9a129bff5:role_14, analysis_5d9c9ae9a129bff5:py_class_b1900e6bc249, analysis_5d9c9ae9a129bff5:py_class_870f0e7b97a3, analysis_5d9c9ae9a129bff5:py_class_90b74f2e9504, analysis_5d9c9ae9a129bff5:py_class_1e5fe54ba53d |
| c14 omml.py (25 outgoing) and latex_dict.py (25 incoming) appear to form a pair that converts Office math markup to LaTeX via the oMath2Latex class. | inferred | supported | analysis_5d9c9ae9a129bff5:role_20, analysis_5d9c9ae9a129bff5:role_19, analysis_5d9c9ae9a129bff5:py_class_54034cf76a50 |
| c15 _xlsx_converter.py and _pptx_converter.py have zero resolved incoming calls, which is consistent with converters being registered and dispatched indirectly. | inferred | supported | analysis_5d9c9ae9a129bff5:role_43, analysis_5d9c9ae9a129bff5:role_39, analysis_5d9c9ae9a129bff5:py_class_b026ac93be11, analysis_5d9c9ae9a129bff5:py_class_164537a7db47 |
| c16 Dependency records come from four pyproject.toml manifests; markitdown's recorded runtime deps include beautifulsoup4, requests, certifi, markdownify, magika, charset-normalizer and defusedxml. | observed | supported | analysis_5d9c9ae9a129bff5:ev_manifest_1, 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 |
| c17 markitdown's optional deps include python-pptx, mammoth, pandas, openpyxl, xlrd, lxml, pdfminer.six, pdfplumber, olefile, pydub, SpeechRecognition, youtube-transcript-api and Azure packages. | 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 |
| c18 markitdown-mcp depends on mcp >=2.1.1,<3.0.0 and on markitdown. | observed | supported | analysis_5d9c9ae9a129bff5:dep_1, analysis_5d9c9ae9a129bff5:dep_2 |
| c19 markitdown-ocr depends on markitdown, pdfminer.six, pdfplumber, PyMuPDF, mammoth, python-docx, python-pptx, pandas, openpyxl and Pillow, with openai as an optional dependency. | observed | supported | analysis_5d9c9ae9a129bff5:dep_3, 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 |
| c20 markitdown-sample-plugin depends on markitdown >=0.1.0a1 and striprtf. | observed | supported | analysis_5d9c9ae9a129bff5:dep_14, analysis_5d9c9ae9a129bff5:dep_15 |
| c21 Several optional records repeat the same name and line (e.g. python-pptx at line 39, azure-identity at line 53); the packet does not explain why. | inferred | supported | analysis_5d9c9ae9a129bff5:dep_23, analysis_5d9c9ae9a129bff5:dep_38, analysis_5d9c9ae9a129bff5:dep_52, analysis_5d9c9ae9a129bff5:dep_54 |
| c22 Only requirements files, package.json and pyproject.toml are parsed for dependencies; setup.py, setup.cfg, Pipfile and lock files are not, and versions are recorded as written. | observed | supported | analysis_5d9c9ae9a129bff5:lim_3a |
| c23 The analyzer counts 112 test or test-like files; the sampled list includes fixture documents, so not all are test code. | inferred | supported | analysis_5d9c9ae9a129bff5:ev_tests_1 |
| c24 Per-format test modules for CSV, DOCX, EPUB, HTML, PDF, PPTX, XLSX and ZIP each contain a __main__ guard that calls pytest.main. | observed | supported | analysis_5d9c9ae9a129bff5:py_entry_6da5faf654d3, analysis_5d9c9ae9a129bff5:py_entry_e1644548438f, analysis_5d9c9ae9a129bff5:py_entry_fd2581a2a85a, analysis_5d9c9ae9a129bff5:py_entry_c1e9a0696ede, analysis_5d9c9ae9a129bff5:py_entry_d48046c8aa24, analysis_5d9c9ae9a129bff5:py_entry_f19b18e9138b, analysis_5d9c9ae9a129bff5:py_entry_fc521ad126e1, analysis_5d9c9ae9a129bff5:py_entry_98eaed3ae984 |
| c25 README.md and LICENSE are flagged by the analyzer as project-level important files. | observed | supported | analysis_5d9c9ae9a129bff5:important_1, analysis_5d9c9ae9a129bff5:important_2 |
| c26 A suggested reading order combines important files with connected modules: start at packages/markitdown/src/markitdown/__main__.py, then _markitdown.py with MarkItDown, ConverterRegistration and _load_plugins. | inferred | supported | analysis_5d9c9ae9a129bff5:important_6, analysis_5d9c9ae9a129bff5:role_13, analysis_5d9c9ae9a129bff5:py_class_54565613c36d, analysis_5d9c9ae9a129bff5:py_class_a5c27a19fe56, analysis_5d9c9ae9a129bff5:py_func_575e8ec2d882 |
| c27 Reading _base_converter.py, _stream_info.py and _exceptions.py next is suggested, because they hold shared types that many modules call into. | inferred | supported | analysis_5d9c9ae9a129bff5:role_11, analysis_5d9c9ae9a129bff5:role_14, analysis_5d9c9ae9a129bff5:role_12, analysis_5d9c9ae9a129bff5:py_class_b1900e6bc249 |
| c28 converters/_html_converter.py (HtmlConverter) has both incoming (6) and outgoing (4) calls, which makes it a reasonable concrete converter to read. | inferred | supported | analysis_5d9c9ae9a129bff5:role_31, analysis_5d9c9ae9a129bff5:py_class_048314abbf0a |
| c29 The MCP entry, its test_stdio_protocols.py test and the sample plugin test are flagged as likely entrypoints and are suggested for reading after the core. | inferred | supported | analysis_5d9c9ae9a129bff5:important_3, analysis_5d9c9ae9a129bff5:important_4, analysis_5d9c9ae9a129bff5:important_5 |
| c30 Of 6816 static relations, 5812 are external or unresolved and 1004 resolve locally. | observed | supported | analysis_5d9c9ae9a129bff5:relation_counts |
| c31 Analysis is static only, and the core has a _load_plugins function, so which converters and plugins are active at runtime cannot be established. | inferred | supported | analysis_5d9c9ae9a129bff5:lim_1, analysis_5d9c9ae9a129bff5:py_func_575e8ec2d882, analysis_5d9c9ae9a129bff5:important_5 |
| c32 Install, run and build inference is partial and installation commands are not verified, so this asset gives no install or run instructions. | observed | supported | analysis_5d9c9ae9a129bff5:lim_2 |
| c33 The analyzer's teaching notes conflict with the packet: one says no bounded execution path exists although paths are present, and another names test_cli_vectors.py as the starting point. | inferred | supported | analysis_5d9c9ae9a129bff5:claim_4d30ade3e21e, analysis_5d9c9ae9a129bff5:claim_34d2322830c1, analysis_5d9c9ae9a129bff5:exec_11e5ff5e359f |
| c34 Files over 400 kB, minified bundles and vendored directories are inventoried but not parsed under the analyzer's bounds. | observed | supported | analysis_5d9c9ae9a129bff5:lim_6 |
| c35 Dynamic dispatch, reflection and runtime framework behavior are outside what static analysis can establish here. | inferred | supported | analysis_5d9c9ae9a129bff5:claim_7c9925f9c8f4, analysis_5d9c9ae9a129bff5:lim_1 |
| c36 Whether any entrypoint actually runs, and what output it produces, is not established by this analysis. | unresolved | supported | analysis_5d9c9ae9a129bff5:lim_2, analysis_5d9c9ae9a129bff5:claim_7c9925f9c8f4 |
來源、權利與說明 · attribution-license-templates/v0.1
權利聲明。原始 repository 託管於 GitHub。其原始碼、文件、名稱、媒體與相關素材的權利,仍屬各自的作者、貢獻者與其他權利人所有,並受該 repository 的授權條款約束。
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.
平台聲明。GitHub 是所連結 repository 的來源託管平台。GitHub 與相關標誌為 GitHub, Inc. 的商標。除非另有明確說明,EVEMISS Technology 與 GitHub 之間沒有隸屬或背書關係。
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.
這一頁怎麼來的。本頁由對應版本的 repository 分析與 AI 輔助的編輯工具產生。技術陳述綁定所分析的版本;原始 repository 更新後,可能重新驗證。
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 輔助分析,並經 EVEMISS Technology 人工與 AI 協力審閱。 · 回報權利疑慮 · 所有 repository 指南