complydoc 0.4.9

Document analysis for LLM pipelines, fully offline.

complydoc inspects documents, and the output of document loaders, before they are sent to an LLM. It measures what processing them will cost, how reliably text can be read off each page, which personal and financial identifiers they contain, and whether anything hidden in a file is addressed to a model.

Quickstart

uv tool install complydoc
complydoc audit ./documents

import complydoc as cd

report = cd.full_audit("./documents")
print(report.overall.score)
cd.write_html(report, "report.html")

Output from a LangChain or LlamaIndex loader, or several loaders over a folder:

from langchain_community.document_loaders import PDFPlumberLoader, PyPDFLoader

report = cd.inspect_documents(PyPDFLoader("contract.pdf"))

report = cd.compare_loaders(
    {"pypdf": PyPDFLoader, "pdfplumber": PDFPlumberLoader, "docling": cd.parsers.docling()},
    paths="./contracts",
    facts=["Payment is due within thirty days"],
)
report.to_pandas("loaders")

Works with LangChain, LlamaIndex, Unstructured, Docling, LlamaParse and Azure AI Document Intelligence, and with any loader that has a load method or is a callable. Reports tag each loader with the framework and library it comes from.

The same from the command line, for CI:

complydoc routing ./documents
complydoc compare-loaders loaders.yaml
complydoc chunks ./documents --splitter "langchain_text_splitters:RecursiveCharacterTextSplitter chunk_size=800"
complydoc diff baseline.json .complydoc/complydoc.json
complydoc check ./documents --policy policy.yaml --markdown summary.md --sarif results.sarif
complydoc clean ./documents --out clean/

check holds a folder to rules written in YAML and exits non-zero when they fail, with a summary for a pull request comment and SARIF for code scanning. clean writes safe copies: the identifiers masked, the metadata removed, and PDFs rasterised on request.

A parser can hang on a malformed file: --timeout 120 gives each document a deadline and lists the ones it stopped.

Optional extras

A plain install reads documents, prices them, measures extraction readiness and finds identifiers by pattern. Two things are optional because they are large:

uv tool install "complydoc[ocr,multilingual-names]"
uv run python -c "from transformers import pipeline; \
    pipeline('token-classification', model='Babelscape/wikineural-multilingual-ner')"

The second command downloads the name model once. Nothing is downloaded while a scan runs, so the model has to be fetched before it can be used.

Names are the part worth understanding before choosing. With multilingual-names they are read by a multilingual model; without it, by spaCy's small English one, which misses names in other languages and mistakes field labels for companies. Neither is a checksum, so both miss some names: Detection accuracy publishes the measured numbers for each.

typesafe is the one extra that changes where your documents go: it sends the passages it judges to a hosted service, and nothing else in complydoc leaves the machine. It is off unless the caller passes allow_network=True, and the guard blocks it otherwise.

complydoc doctor shows what is installed, and complydoc benchmark prints what detection finds and what it wrongly flags against a labelled corpus that ships with the package.

What it reports

• Formats: PDF, scans and images, Word, Excel, PowerPoint, HTML, Markdown, plain text and email (.eml).
• Token cost: text and vision tokens per document, priced across models and three extraction paths (text layer, OCR, vision).
• Page routing: the path each page needs — its text layer, local OCR or a vision model — with the reason, priced as a mix against sending everything one way, and written as a manifest an ingestion job can read.
• Extraction readiness: measured signals such as text layer coverage, tables, columns, rotation, scan resolution, garbled characters, glyph codes and repeated headers.
• Identifiers: personal and financial identifiers from Europe, the Americas, India and Australia, checksum-validated where a checksum exists, masked in every output.
• Hidden content and prompt injection: text a reader does not see and a model does (white or invisible text, hidden formatting, Unicode tag characters), and passages that read as instructions to a model.
• Loader inspection and comparison: what a loader extracted, the metadata it attached, the network connections it attempted, and where several loaders disagree, over a single input or a folder, with failures, load time and estimated parser cost per loader.
• Expected facts: whether passages you expect appear in each loader's text, as exact or fuzzy matches.
• Parser presets: Docling, Unstructured, LlamaParse and Azure Document Intelligence; hosted parsers run only with allow_network=True.
• Tables: every part of a report as a pandas DataFrame, and a summary in Jupyter.
• Python API: scanning and masking strings, chunk inspection, baselines with diffs and assertions for tests, streaming audits, cached loader output, and pipeline steps for LangChain and LlamaIndex.
• Masked text: the documents' text with identifiers covered, chunked and counted in tokens.
• Safe copies: the same document with its identifiers masked and its metadata removed, for text, Markdown, HTML, email and Office files. A PDF copy has its metadata stripped and can be rasterised, which leaves no text layer to read.
• Measured accuracy: what identifier detection finds and what it wrongly flags, scored against a labelled corpus that ships with the package and published with the numbers.

How it works

• Offline: outbound sockets and DNS lookups are blocked for the whole run, and each report records that the guard was armed.
• Unmeasured values: a signal that cannot be measured is reported as unmeasured and left out of scores.
• Evidence tiers: every finding states how it was established, whether by checksum, corroboration, pattern or model.
• Configurable: prices, signal weights and detection patterns are YAML files, and name detection can use your own spaCy models, per language, or any other model as a detector.
• One report: a self-contained HTML file and a JSON file with a versioned schema.

Resources

• Documentation: guides and design notes
• Command line reference
• Python API reference
• Playground: runnable command line and Python examples, with a CI workflow
• Report JSON
• Changelog
• Contributing

License

MIT