NameetP/pdfmux

v1.7.0 Breaking

This release includes 3 breaking changes for platform teams planning a safe upgrade.

Published 1mo Developer Productivity

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai-agent docling document-parsing llm mcp ocr

+8 more

opendataloader pdf pdf-extraction pdf-to-json pdf-to-markdown python self-healing structured-extraction

Affected surfaces

breaking_upgrade

ReleasePort's take

Moderate signal

editorial:auto 1mo

In pdfmux v1.7.0 the `--strict` flag is now enabled by default and `--min-confidence` defaults to 0.75.

Why it matters: If your workflows rely on relaxed validation, update scripts to explicitly set `--strict=false` or adjust confidence thresholds before upgrading; otherwise stricter checks may reject previously accepted inputs.

Summary

AI summary

--strict is now ON by default and --min-confidence defaults to 0.75, causing low‑confidence conversions to exit with code 3.

Changes in this release

Type	Severity	Summary	CVE
Breaking	High	`--strict` flag is ON by default; `--min-confidence` defaults to 0.75. `--strict` flag is ON by default; `--min-confidence` defaults to 0.75. Source: llm_adapter@2026-06-15 Confidence: high	—
Bugfix	Low	`pdfmux convert` exits with code 3 if any document scores below confidence 0.75. `pdfmux convert` exits with code 3 if any document scores below confidence 0.75. Source: granite4.1:30b@2026-06-15-audit Confidence: low	—

Full changelog

BREAKING: --strict is ON by default; --min-confidence default is now 0.75.

pdfmux convert ./docs/ now exits 3 if any document scores below 0.75 confidence (previously warn-only, exit 0). Safe-by-default replaces opt-in quality gating — the failure mode that drove this was forgetting to pass --strict.

Migration

Restore 1.6.x behaviour: pdfmux convert ./docs/ --no-strict --min-confidence 0.0
Already passing --strict --min-confidence 0.75? That is now just pdfmux convert ./docs/.
CI that always exited 0 will now exit 3 on low-quality batches — fix at intake or pass --no-strict.

Unchanged

All other flags; the programmatic API defaults (overridable per call); audit, mcp, watch, diff.

Calibrated against the 50-fixture eval at precision 1.00. Full notes in CHANGELOG.md.

Published to PyPI on 2026-05-22 (https://pypi.org/project/pdfmux/1.7.0/). This GitHub release backfills the tag (was sitting at v1.6.4 for 3+ weeks).

Breaking Changes

--strict flag is enabled by default (previously opt‑in)
`--min-confidence` default changed from unspecified/0.0 to 0.75
Conversion command now exits with status code 3 when any document's confidence < 0.75 (was exit 0 with a warning)

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track NameetP/pdfmux

Get notified when new releases ship.

About NameetP/pdfmux

PDF extraction router with built-in MCP server. Classifies each page (digital, scanned, tables) and routes to the best backend (PyMuPDF, Docling, OCR, or optional LLM fallback)

All releases →