complydoc
complydoc for Claude: documents opened with personal and financial details masked and hidden instructions taken out.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 19 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/complydoc/complydoc with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/complydoc/complydoc'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/complydoc--complydoc)HTML
<a href="/listings/complydoc--complydoc"><img src="/api/listings/complydoc--complydoc/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 15 lines
- {
- "name": "complydoc",
- "description": "complydoc for Claude: documents opened with personal and financial details masked and hidden instructions taken out.",
- "owner": {
- "name": "complydoc",
- "url": "https://github.com/complydoc"
- },
- "plugins": [
- {
- "name": "complydoc",
- "source": "./plugin",
- "description": "Open documents with personal and financial details masked and hidden instructions taken out, on your machine."
- }
- ]
- }
README.md · README · 110 lines
- <div align="center">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/complydoc/complydoc/main/.github/images/logo-dark.svg">
- <img alt="complydoc" src="https://raw.githubusercontent.com/complydoc/complydoc/main/.github/images/logo-light.svg" width="42%">
- </picture>
- <h3>Get document loading right.</h3>
- <p>Compare loaders, trace every step and evaluate what reaches your model.</p>
- <a href="https://pypi.org/project/complydoc/"><img src="https://img.shields.io/pypi/v/complydoc?color=56b4e0&label=pypi" alt="PyPI"></a>
- <a href="https://github.com/complydoc/complydoc/actions/workflows/checks.yml"><img src="https://github.com/complydoc/complydoc/actions/workflows/checks.yml/badge.svg?branch=main" alt="Tests"></a>
- <a href="https://complydoc.github.io/complydoc/docs/"><img src="https://img.shields.io/badge/docs-complydoc-56b4e0" alt="Documentation"></a>
- <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/license-MIT-56b4e0" alt="License"></a>
- </div>
- <!-- mcp-name: io.github.complydoc/complydoc -->
- <br>
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/complydoc/complydoc/main/.github/images/viewer-trace-dark.webp">
- <img alt="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" src="https://raw.githubusercontent.com/complydoc/complydoc/main/.github/images/viewer-trace-light.webp" width="100%">
- </picture>
- 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
- ```bash
- 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`](examples/hidden_clause.pdf).
- ## In your assistant
- `complydoc mcp` lets Claude, Cursor or any MCP client open documents with personal and
- financial details masked and hidden instructions taken out. In Claude Code:
- ```text
- /plugin install complydoc --marketplace complydoc/complydoc
- ```
- Elsewhere, run it with `uvx complydoc mcp`; it is in the
- [MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.complydoc/complydoc`.
- Claude Desktop installs it from the extension on the
- [releases page](https://github.com/complydoc/complydoc/releases/latest). See
- [Documents into an assistant, cleaned](https://complydoc.github.io/complydoc/docs/guides/assistant-mcp/).
- ## Observe a pipeline
- ```python
- 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
- ```yaml
- - uses: complydoc/complydoc@v0.8.1
- 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](https://complydoc.github.io/complydoc/docs/guides/github-action/).
- ## More
- - [Documentation](https://complydoc.github.io/complydoc/docs/), and the
- [playground](https://github.com/complydoc/playground) with everything ready to run
- - [Run it for your team](https://complydoc.github.io/complydoc/docs/guides/team/), in a
- [container](https://complydoc.github.io/complydoc/docs/guides/container/) or from a bucket
- - [Network isolation](https://complydoc.github.io/complydoc/docs/explanation/offline/): every
- run blocks outbound connections and records that it did
- - Optional extras for scans and names: `complydoc doctor` says what is installed and how to
- add the rest
- - [Changelog](https://github.com/complydoc/complydoc/blob/main/src/complydoc/CHANGELOG.md) ·
- [Contributing](https://github.com/complydoc/complydoc/blob/main/CONTRIBUTING.md) · MIT
- If complydoc is useful to you, a star helps other engineers find it.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.