MinerOS
MinerOS is an Apache 2.0-licensed fork of MinerU — a high-accuracy document parsing engine that converts PDF, Word, PPT, and images into structured Markdown/JSON for LLM · RAG · Agent workflows.
Why "OS"?
MinerU's upstream license history is complicated: the project briefly adopted AGPLv3 before reverting. MinerOS is pinned to the last clean Apache 2.0 commit (e148afa9) and kept Apache 2.0 going forward — making it safe to embed in commercial and government applications without AGPL copyleft concerns.
The OS suffix signals:
- Open Source — fully Apache 2.0, no AGPL, no CC-BY-NC
- Open Standard — suitable for government procurement, regulated industries, and open-data pipelines
- OS-level reliability — designed to run as infrastructure, not just a script
What MinerOS adds over upstream MinerU
| Feature | MinerU upstream | MinerOS |
|---|---|---|
| License | Briefly AGPLv3, reverted | Apache 2.0 throughout |
| Tracked-changes / strikethrough detection | ❌ | ✅ (~~struck text~~ in Markdown) |
Remote VLM via .env auto-config |
manual | .env loaded automatically |
| Package name | mineru |
mineros |
Core Parsing Capabilities
- PDF · DOCX · PPTX · Images → Markdown + JSON
- Tracked-changes detection — renders struck-through text as
~~...~~in Markdown output (critical for government contracts, legislative drafts, redlined legal documents) - Formulas → LaTeX · Tables → HTML · accurate layout reconstruction
- Scanned docs, handwriting, multi-column layouts, cross-page table merging
- Output follows human reading order with automatic header/footer removal
- VLM + OCR dual engine, 109-language OCR recognition
Deployment Backends
| Backend | Best For |
|---|---|
pipeline |
Fast & stable, no hallucination, runs on CPU or GPU |
vlm-http-client |
High accuracy via remote OpenAI-compatible VLM server (e.g., Azure llama.cpp) |
hybrid-http-client |
High accuracy + local OCR, minimal local VRAM |
vlm-auto-engine |
High accuracy via local vLLM / LMDeploy / mlx |
hybrid-auto-engine |
Best accuracy, native text extraction, low hallucination |
Quick Start
Install
pip install uv
uv pip install -e ".[core]"
Or from PyPI (once published):
uv pip install "mineros[core]"
Run
# Basic parsing (auto-selects best available backend)
mineros -p <input.pdf> -o <output_dir>
# CPU-only (pipeline backend)
mineros -p <input.pdf> -o <output_dir> -b pipeline
# Remote VLM server (reads MINERU_VL_SERVER / MINERU_VL_API_KEY / MINERU_VL_MODEL_NAME from .env)
mineros -p <input.pdf> -o <output_dir> -b vlm-http-client
# Specific page range
mineros -p <input.pdf> -o <output_dir> -b vlm-http-client -s 0 -e 3
Environment Variables (.env)
# Remote VLM server (OpenAI-compatible)
MINERU_VL_SERVER=https://your-llm-server.example.com
MINERU_VL_API_KEY=your-api-key
MINERU_VL_MODEL_NAME=your-model-name
# Required when server n_ctx is small (e.g., llama.cpp with 8192 context)
MINEROS_PROCESSING_WINDOW_SIZE=1
The .env file is loaded automatically via python-dotenv — no manual export needed.
Hardware Requirements
| Backend | pipeline | *-auto-engine | *-http-client | ||
|---|---|---|---|---|---|
| hybrid | vlm | hybrid | vlm | ||
| Pure CPU | ✅ | ❌ | ✅ | ||
| Min VRAM | 4 GB | 8 GB | 8 GB | 2 GB | None |
| Min RAM | 16 GB (32 GB recommended) | 16 GB | |||
| Python | 3.10 – 3.13 | ||||
| OS | Linux (2019+) · Windows · macOS 14+ | ||||
Docker
# Build
docker build -f docker/global/Dockerfile -t mineros:latest .
# Run via Compose
docker compose -f docker/compose.yaml up
Known Issues
- Reading order may be out of sequence in extremely complex multi-column layouts.
- Strikethrough detection relies on the VLM visually identifying struck text — accuracy depends on model capability and image resolution.
- Tables of contents and lists are recognized via rules; uncommon formats may be missed.
- Comic books, art albums, and heavily stylized documents parse poorly.
- OCR may produce inaccurate characters for lesser-known languages.
License
MinerOS is a derivative of MinerU (opendatalab), used and redistributed under the terms of the Apache 2.0 license as it existed at commit e148afa9. All modifications are also released under Apache 2.0.
Acknowledgments
MinerOS stands on the shoulders of MinerU and its dependencies:
Metadata
Release files for mineros 3.0.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mineros-3.0.11.tar.gz | 1.4 MB | With provenance | Details for mineros-3.0.11.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mineros-3.0.11-py3-none-any.whl | Python 3 | none | any | Details for mineros-3.0.11-py3-none-any.whl |
Total release size: 2.8 MB
Release files / mineros-3.0.11.tar.gz
| Download URL | mineros-3.0.11.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07f1b3d1f21b395cbedee1136b40ae06d62fb0fb17f8fd09892a0f7776e0c96c
|
|
BLAKE2b-256 checksum How to use checksums |
1fa101e00d38c1ac2e581372c45540bb0ddbcbbb8ef68665800ac438a7a2cb4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 16, 2026.
Transparency logRelease files / mineros-3.0.11-py3-none-any.whl
| Download URL | mineros-3.0.11-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6dadf3b07344b7b295a1d99bbf979eaa1bd31f7e7a4312276800a595e973572
|
|
BLAKE2b-256 checksum How to use checksums |
d7bca2ad84e9ac811eb10f63f25b1ec84390907448d62a86a83356a4b24fd3d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 16, 2026.
Transparency logSecurity for mineros 3.0.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mineros-3.0.11.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.