Skip to content
Back to search

complydoc

MarketplaceWorks with Claude CodeGitHub

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.

Checked today

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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/complydoc--complydoc/badge.svg)](/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
  1. {
  2. "name": "complydoc",
  3. "description": "complydoc for Claude: documents opened with personal and financial details masked and hidden instructions taken out.",
  4. "owner": {
  5. "name": "complydoc",
  6. "url": "https://github.com/complydoc"
  7. },
  8. "plugins": [
  9. {
  10. "name": "complydoc",
  11. "source": "./plugin",
  12. "description": "Open documents with personal and financial details masked and hidden instructions taken out, on your machine."
  13. }
  14. ]
  15. }
README.md · README · 110 lines
  1. <div align="center">
  2. <picture>
  3. <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/complydoc/complydoc/main/.github/images/logo-dark.svg">
  4. <img alt="complydoc" src="https://raw.githubusercontent.com/complydoc/complydoc/main/.github/images/logo-light.svg" width="42%">
  5. </picture>
  6. <h3>Get document loading right.</h3>
  7. <p>Compare loaders, trace every step and evaluate what reaches your model.</p>
  8. <a href="https://pypi.org/project/complydoc/"><img src="https://img.shields.io/pypi/v/complydoc?color=56b4e0&label=pypi" alt="PyPI"></a>
  9. <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>
  10. <a href="https://complydoc.github.io/complydoc/docs/"><img src="https://img.shields.io/badge/docs-complydoc-56b4e0" alt="Documentation"></a>
  11. <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/license-MIT-56b4e0" alt="License"></a>
  12. </div>
  13. <!-- mcp-name: io.github.complydoc/complydoc -->
  14. <br>
  15. <picture>
  16. <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/complydoc/complydoc/main/.github/images/viewer-trace-dark.webp">
  17. <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%">
  18. </picture>
  19. A PDF can say one thing to a person and another to your model. White text, tiny type, an
  20. IBAN behind a black bar: it's all still in the text layer, and most loaders pass it straight
  21. through. complydoc shows what your loaders actually extracted, flags hidden text and
  22. personal and financial identifiers before they're embedded, and traces every ingestion step
  23. with its time and cost. Nothing leaves your machine.
  24. Works with LangChain, LlamaIndex, Unstructured, Haystack, Docling, LlamaParse, Azure
  25. Document Intelligence, Marker, Chonkie and the common vector stores and embedding APIs.
  26. ## Try it
  27. ```bash
  28. uv tool install complydoc
  29. complydoc ui ./documents
  30. ```
  31. `complydoc ui` audits the folder and opens the viewer on it, served from your machine. To
  32. see a hidden clause caught, try the one-page contract in
  33. [`examples/hidden_clause.pdf`](examples/hidden_clause.pdf).
  34. ## In your assistant
  35. `complydoc mcp` lets Claude, Cursor or any MCP client open documents with personal and
  36. financial details masked and hidden instructions taken out. In Claude Code:
  37. ```text
  38. /plugin install complydoc --marketplace complydoc/complydoc
  39. ```
  40. Elsewhere, run it with `uvx complydoc mcp`; it is in the
  41. [MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.complydoc/complydoc`.
  42. Claude Desktop installs it from the extension on the
  43. [releases page](https://github.com/complydoc/complydoc/releases/latest). See
  44. [Documents into an assistant, cleaned](https://complydoc.github.io/complydoc/docs/guides/assistant-mcp/).
  45. ## Observe a pipeline
  46. ```python
  47. import complydoc as cd
  48. with cd.observe("contracts-ingest"):
  49. documents = PyMuPDF4LLMLoader("contract.pdf").load()
  50. chunks = splitter.split_documents(documents)
  51. vector_store.add_documents(chunks)
  52. ```
  53. Every loader, splitter, embedding call and vector store becomes a step, with its settings,
  54. time, tokens, cost and the identifiers it passed on. Open it with `complydoc ui`.
  55. ## What it shows
  56. - **Traces** of each ingestion step, and how runs compare over time.
  57. - **Loader diffs**: each loader's reading of a page side by side, with the page itself.
  58. - **Identifiers** from Europe, the Americas, India and Australia, checksum-validated and
  59. masked until you choose to see them.
  60. - **Hidden content**: text a reader does not see and a model does, and instructions
  61. written to a model.
  62. - **Evals**: the facts a document must keep, checked on every reading.
  63. - **Chunks and cost**: splitters side by side, and tokens priced across models.
  64. ## In CI
  65. ```yaml
  66. - uses: complydoc/complydoc@v0.8.1
  67. with:
  68. path: documents
  69. policy: policy.yaml
  70. ```
  71. `complydoc check` fails when a folder breaks your rules; `finance`, `legal` and `hr` ship as
  72. ready policies. See [GitHub Action](https://complydoc.github.io/complydoc/docs/guides/github-action/).
  73. ## More
  74. - [Documentation](https://complydoc.github.io/complydoc/docs/), and the
  75. [playground](https://github.com/complydoc/playground) with everything ready to run
  76. - [Run it for your team](https://complydoc.github.io/complydoc/docs/guides/team/), in a
  77. [container](https://complydoc.github.io/complydoc/docs/guides/container/) or from a bucket
  78. - [Network isolation](https://complydoc.github.io/complydoc/docs/explanation/offline/): every
  79. run blocks outbound connections and records that it did
  80. - Optional extras for scans and names: `complydoc doctor` says what is installed and how to
  81. add the rest
  82. - [Changelog](https://github.com/complydoc/complydoc/blob/main/src/complydoc/CHANGELOG.md) ·
  83. [Contributing](https://github.com/complydoc/complydoc/blob/main/CONTRIBUTING.md) · MIT
  84. If complydoc is useful to you, a star helps other engineers find it.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.