Skip to main content
complydoc

Know your documents before they reach an LLM.

An open-source, offline audit for documents before they're indexed.

PyPI Tests Documentation License


The complydoc viewer: a LangChain ingestion pipeline traced step by step, each loader, splitter, vector store and embedding call on a time axis with its time, cost and the identifiers it passed on

A PDF can say one thing to a person and another to your model. White text, tiny type, an IBAN behind a black bar: it's all still in the text layer, and most loaders pass it straight through. complydoc shows what your loaders actually extracted, flags hidden text and personal and financial identifiers before they're embedded, and traces every ingestion step with its time and cost. Nothing leaves your machine.

Works with LangChain, LlamaIndex, Unstructured, Haystack, Docling, LlamaParse, Azure Document Intelligence, Marker, Chonkie and the common vector stores and embedding APIs.

Try it

uv tool install complydoc
complydoc ui ./documents

complydoc ui audits the folder and opens the viewer on it, served from your machine. To see a hidden clause caught, try the one-page contract in examples/hidden_clause.pdf.

Observe a pipeline

import complydoc as cd

with cd.observe("contracts-ingest"):
    documents = PyMuPDF4LLMLoader("contract.pdf").load()
    chunks = splitter.split_documents(documents)
    vector_store.add_documents(chunks)

Every loader, splitter, embedding call and vector store becomes a step, with its settings, time, tokens, cost and the identifiers it passed on. Open it with complydoc ui.

What it shows

  • Traces of each ingestion step, and how runs compare over time.
  • Loader diffs: each loader's reading of a page side by side, with the page itself.
  • Identifiers from Europe, the Americas, India and Australia, checksum-validated and masked until you choose to see them.
  • Hidden content: text a reader does not see and a model does, and instructions written to a model.
  • Evals: the facts a document must keep, checked on every reading.
  • Chunks and cost: splitters side by side, and tokens priced across models.

In CI

- uses: complydoc/complydoc@v0.7.13
  with:
    path: documents
    policy: policy.yaml

complydoc check fails when a folder breaks your rules; finance, legal and hr ship as ready policies. See GitHub Action.

More

Metadata

Release files for complydoc 0.7.13

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for complydoc 0.7.13
File Size Uploaded Provenance Actions
complydoc-0.7.13.tar.gz 6.6 MB With provenance Details for complydoc-0.7.13.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for complydoc 0.7.13
File Interpreter ABI Platform Actions
complydoc-0.7.13-py3-none-any.whl Python 3 none any Details for complydoc-0.7.13-py3-none-any.whl

Total release size: 10.8 MB

Release files / complydoc-0.7.13.tar.gz

Download URL complydoc-0.7.13.tar.gz
Size 6.6 MB
Tags Source
SHA-256 checksum
How to use checksums
df353400f83e821d2ef48cdc4893c8f368393ed60c09fd5bbc3f98be91fdbf52
BLAKE2b-256 checksum
How to use checksums
c1589609d6bb73cacf53fc4dfe16ebbad89a962dad77ea088c4f87d8d711e7f9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 17, 2026.

Transparency log

Release files / complydoc-0.7.13-py3-none-any.whl

Download URL complydoc-0.7.13-py3-none-any.whl
Size 4.2 MB
Tags Python 3
SHA-256 checksum
How to use checksums
dec1bd1592e94a855f5e42650f5583370c998b1fa5ffe198cb334a4470eca9d6
BLAKE2b-256 checksum
How to use checksums
ca9efc3518ba9ec44107c4e6470d17eab4aa38bc690c0f24b94006eccb51156d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 17, 2026.

Transparency log

Security for complydoc 0.7.13

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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for complydoc-0.7.13.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 Nov 17, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release

0.7.13 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page