vault-engine 0.1.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (37) hide show
  1. vault_engine-0.1.0/LICENSE +201 -0
  2. vault_engine-0.1.0/NOTICE +6 -0
  3. vault_engine-0.1.0/PKG-INFO +270 -0
  4. vault_engine-0.1.0/README.md +246 -0
  5. vault_engine-0.1.0/pyproject.toml +45 -0
  6. vault_engine-0.1.0/setup.cfg +4 -0
  7. vault_engine-0.1.0/tests/test_cli.py +100 -0
  8. vault_engine-0.1.0/tests/test_clip.py +81 -0
  9. vault_engine-0.1.0/tests/test_detectors.py +54 -0
  10. vault_engine-0.1.0/tests/test_formats.py +44 -0
  11. vault_engine-0.1.0/tests/test_mapping.py +98 -0
  12. vault_engine-0.1.0/tests/test_pipeline.py +64 -0
  13. vault_engine-0.1.0/tests/test_providers.py +73 -0
  14. vault_engine-0.1.0/tests/test_roundtrip.py +69 -0
  15. vault_engine-0.1.0/vault_engine.egg-info/PKG-INFO +270 -0
  16. vault_engine-0.1.0/vault_engine.egg-info/SOURCES.txt +35 -0
  17. vault_engine-0.1.0/vault_engine.egg-info/dependency_links.txt +1 -0
  18. vault_engine-0.1.0/vault_engine.egg-info/entry_points.txt +2 -0
  19. vault_engine-0.1.0/vault_engine.egg-info/requires.txt +3 -0
  20. vault_engine-0.1.0/vault_engine.egg-info/top_level.txt +1 -0
  21. vault_engine-0.1.0/vaultengine/__init__.py +28 -0
  22. vault_engine-0.1.0/vaultengine/__main__.py +10 -0
  23. vault_engine-0.1.0/vaultengine/cli.py +269 -0
  24. vault_engine-0.1.0/vaultengine/clipboard.py +71 -0
  25. vault_engine-0.1.0/vaultengine/config.py +96 -0
  26. vault_engine-0.1.0/vaultengine/detectors.py +88 -0
  27. vault_engine-0.1.0/vaultengine/formats.py +59 -0
  28. vault_engine-0.1.0/vaultengine/mapping.py +205 -0
  29. vault_engine-0.1.0/vaultengine/pipeline.py +126 -0
  30. vault_engine-0.1.0/vaultengine/prompts.py +103 -0
  31. vault_engine-0.1.0/vaultengine/providers/__init__.py +14 -0
  32. vault_engine-0.1.0/vaultengine/providers/base.py +164 -0
  33. vault_engine-0.1.0/vaultengine/providers/null.py +25 -0
  34. vault_engine-0.1.0/vaultengine/providers/ollama.py +67 -0
  35. vault_engine-0.1.0/vaultengine/providers/openai_compat.py +61 -0
  36. vault_engine-0.1.0/vaultengine/report.py +129 -0
  37. vault_engine-0.1.0/vaultengine/spans.py +117 -0
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2026 fishonbike
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,6 @@
1
+ vault-engine
2
+ Copyright 2026 fishonbike
3
+
4
+ Licensed under the Apache License, Version 2.0 (see LICENSE).
5
+
6
+ This product includes software developed by fishonbike.
@@ -0,0 +1,270 @@
1
+ Metadata-Version: 2.4
2
+ Name: vault-engine
3
+ Version: 0.1.0
4
+ Summary: Identity de-identification for cloud-LLM hand-off: local detection, consistent pseudonyms, a reversible local map, and a swappable model backend.
5
+ Author: fishonbike
6
+ License: Apache-2.0
7
+ Project-URL: Source, https://github.com/fishonbike/vault-engine
8
+ Project-URL: Issues, https://github.com/fishonbike/vault-engine/issues
9
+ Keywords: privacy,pii,de-identification,anonymization,redaction,pseudonymization,llm,ollama,qwen,egress
10
+ Classifier: Development Status :: 4 - Beta
11
+ Classifier: Intended Audience :: Developers
12
+ Classifier: License :: OSI Approved :: Apache Software License
13
+ Classifier: Operating System :: OS Independent
14
+ Classifier: Programming Language :: Python :: 3
15
+ Classifier: Topic :: Security
16
+ Classifier: Topic :: Text Processing :: Filters
17
+ Requires-Python: >=3.9
18
+ Description-Content-Type: text/markdown
19
+ License-File: LICENSE
20
+ License-File: NOTICE
21
+ Provides-Extra: dev
22
+ Requires-Dist: pytest; extra == "dev"
23
+ Dynamic: license-file
24
+
25
+ # vault-engine
26
+
27
+ **A local-LLM privacy layer for anything you paste into a cloud model.**
28
+
29
+ Strip the identities out of your text *before* it reaches ChatGPT / Claude /
30
+ Gemini — a model running **on your own machine** finds the names, orgs, places
31
+ and quasi-identifiers, replaces them with stable tokens, and keeps the only
32
+ key-back-to-reality on disk. When the cloud answers in tokens, you put the real
33
+ identities back locally.
34
+
35
+ > 出云前做身份脱敏:本地模型检测 → 代号化 → 云端用代号分析 → 本地还原真身。
36
+ > 检测**不出本机**,身份映射**只存本地**,大模型**一行换**。零依赖。
37
+
38
+ <p align="center">
39
+ <img src="docs/demo.svg" alt="vault-engine scrubs English and Chinese names and PII into tokens before the cloud sees them, then restores them locally" width="760">
40
+ </p>
41
+
42
+ ![CI](https://github.com/fishonbike/vault-engine/actions/workflows/ci.yml/badge.svg)
43
+ &nbsp;·&nbsp; Python ≥3.9 &nbsp;·&nbsp; stdlib-only &nbsp;·&nbsp; Apache-2.0
44
+
45
+ ```text
46
+ # notes.txt ── private, on your machine
47
+ 林若曦是星澜资本的合伙人,在深圳见了字节跳动的陈大壮,邮箱 lin@xinglan.example
48
+
49
+ ▼ vault-engine scrub (local qwen3.6:27b)
50
+
51
+ # safe.txt ── what the cloud sees: identities swapped for tokens
52
+ P-n1 是 ORG_1 的合伙人,在 LOC_1 见了 ORG_2 的 P-n2,邮箱 EMAIL_1
53
+ ```
54
+
55
+ ---
56
+
57
+ ## Why
58
+
59
+ You want a frontier cloud model to analyze sensitive notes — but you don't want
60
+ the cloud to learn *who* they're about. Masking only the names you already know
61
+ leaks everything you don't: an unregistered name, an employer, a city + a rare
62
+ title, a project codename. Pattern-based redaction never sees those at all.
63
+
64
+ `vault-engine` puts a **local model** in front as the detector, so the semantic
65
+ identifiers get caught too — and nothing but the sanitized text ever leaves.
66
+
67
+ ## How it works
68
+
69
+ ```
70
+ private text cloud model
71
+ │ (sees only tokens)
72
+ ▼ ▲
73
+ ┌─────────────────────────── vault-engine ────────────┼───────────┐
74
+ │ ① regex PII detectors (offline floor) │ │
75
+ │ ② LLM detector (local model finds names, │ │
76
+ │ orgs, places, quasi-IDs) │ │
77
+ │ ③ consistent pseudonyms (张三→P-n1, 同名同号) │ │
78
+ │ ④ residual-risk critic (re-scan: anything left?) │ ① send │
79
+ │ │ │ │
80
+ │ sanitized text ────────────────────────────────────┘ │
81
+ │ ▲ │
82
+ │ reverse map (token → real identity) ── stays LOCAL ──┐ ② reply │
83
+ │ └───────────────────── ⑤ rehydrate ◀────────────┘ │
84
+ └──────────────────────────────────────────────────────────────────┘
85
+
86
+ real identities restored locally → use in your own system
87
+ ```
88
+
89
+ ## Benchmark
90
+
91
+ How much identity each detector actually catches, on a labelled bilingual
92
+ dataset (reproduce with `python eval/run_eval.py`; methodology in
93
+ [`eval/`](eval/README.md)):
94
+
95
+ <!-- BENCHMARK:START -->
96
+ 77 gold identities across 15 bilingual documents — easy PII plus hard cases
97
+ (ambiguous common-word names, abbreviations, transliterations, @handles, a badge
98
+ number, a license plate). Reproduce:
99
+ `python eval/run_eval.py --provider ollama --with-presidio`.
100
+
101
+ > ⚠️ A **small synthetic set** for regression testing and rough comparison —
102
+ > **not** evidence of legal anonymization or complete privacy. "Recall" means
103
+ > flagged-for-redaction; LLM detection is non-deterministic. See the
104
+ > [threat model](#threat-model--limitations-honest).
105
+
106
+ | detector | person | org | location | project | contact | id | **overall** | over-redaction |
107
+ |---|---|---|---|---|---|---|---|---|
108
+ | regex only | 0% | 0% | 0% | 0% | 69% | 33% | **13%** | 0% |
109
+ | Microsoft Presidio (en/zh `lg`) | 78% | 59% | 80% | 33% | 38% | 0% | **61%** | 4% |
110
+ | **vault-engine (qwen3.6:27b)** | 100% | 100% | 100% | 100% | 100% | 100% | **100%** | 0% |
111
+
112
+ Same set where Presidio's NER scores 61%, the local LLM clears 100% — gap widest
113
+ on codenames, @handles, IDs, and Chinese names/orgs. Trade-off is speed: Presidio
114
+ ~6s, the LLM ~25s/doc.
115
+ <!-- BENCHMARK:END -->
116
+
117
+ The point isn't a leaderboard — it's the **shape**: pattern-only redaction can't
118
+ see names, organizations, locations, or codenames at all; a local LLM can.
119
+
120
+ ## Install
121
+
122
+ ```bash
123
+ pip install vault-engine
124
+ ```
125
+
126
+ Or get the latest straight from source:
127
+
128
+ ```bash
129
+ pip install git+https://github.com/fishonbike/vault-engine
130
+ ```
131
+
132
+ For the default local backend, install [Ollama](https://ollama.com) and pull a
133
+ model:
134
+
135
+ ```bash
136
+ ollama pull qwen3.6:27b
137
+ ```
138
+
139
+ No model yet? The deterministic floor (emails, phones, IDs, cards, URLs) works
140
+ with zero setup via `--no-llm`.
141
+
142
+ ## Quickstart
143
+
144
+ ```bash
145
+ vault-engine scrub notes.txt -o notes.safe.txt
146
+ ```
147
+
148
+ That writes `notes.safe.txt` (send this to the cloud) and
149
+ `notes.safe.txt.map.json` (**local only** — the identities). Paste the sanitized
150
+ text into your model, save its reply, then restore the real identities:
151
+
152
+ ```bash
153
+ vault-engine rehydrate reply.json --map notes.safe.txt.map.json -o reply.real.json
154
+ ```
155
+
156
+ ### The clipboard one-liner
157
+
158
+ The fastest path — scrub whatever you're about to paste into a chatbot, in place:
159
+
160
+ ```bash
161
+ vault-engine clip # de-identifies the clipboard
162
+ # …paste into ChatGPT/Claude, copy its reply, then:
163
+ vault-engine clip --rehydrate # restores the real identities in the clipboard
164
+ ```
165
+
166
+ Works on macOS, Windows, and Linux (with `xclip`/`xsel`/`wl-clipboard`).
167
+
168
+ Library:
169
+
170
+ ```python
171
+ from vaultengine import deidentify, rehydrate, Config
172
+
173
+ result = deidentify(open("notes.txt").read(), Config(model="qwen3.6:27b"))
174
+ send_to_cloud(result.text) # tokens only
175
+ restored = rehydrate(get_cloud_reply(), result.vault) # real identities, locally
176
+ result.vault.save("notes.map.json") # the reverse map — keep it local
177
+ ```
178
+
179
+ ## Use cases
180
+
181
+ - **Pseudonymize before pasting into ChatGPT/Claude** — analyze private notes,
182
+ contracts, or chats with direct identifiers stripped.
183
+ - **Redact logs & support tickets** before sharing them or feeding an LLM.
184
+ - **Anonymize a dataset** for LLM-assisted analysis, then map results back.
185
+ - **Air-gapped review loops** — a model on a locked-down box only ever sees
186
+ tokens.
187
+
188
+ ## How it compares
189
+
190
+ Presidio and LLM Guard are excellent, mature tools. vault-engine's bet is
191
+ different: a **local LLM** as the detector catches semantic/quasi-identifiers
192
+ that label-based NER misses, with **zero runtime deps** and first-class Chinese.
193
+
194
+ | | **vault-engine** | Presidio | LLM Guard (Anonymize) | regex / scrubadub |
195
+ |---|---|---|---|---|
196
+ | Detection | local LLM + regex | NER (spaCy) + regex | NER / transformers | patterns only |
197
+ | Unregistered names / orgs / quasi-IDs | ✅ LLM | ⚠️ NER labels only | ⚠️ NER-limited | ❌ |
198
+ | Reversible round-trip | ✅ local map | ✅ deanonymizer | ✅ Vault | ❌ |
199
+ | Fully local / offline | ✅ Ollama | ✅ | ⚠️ varies | ✅ |
200
+ | Runtime dependencies | **none (stdlib)** | spaCy + models | several | varies |
201
+ | Chinese (中文) | ✅ strong | ⚠️ needs model | ⚠️ | ❌ |
202
+ | Swap the model | ✅ one line | — | partial | — |
203
+ | Fail-loud if detector errors | ✅ degrades + non-zero exit | — | — | — |
204
+
205
+ ## Redaction policy (privacy ↔ utility)
206
+
207
+ | `--policy` | Persons | Orgs / places / roles | Dates | Token shape |
208
+ |-------------|---------|-----------------------|-------|-------------|
209
+ | `balanced` *(default)* | ✅ | ✅ typed (`ORG_1`, `LOC_2`) | kept | typed |
210
+ | `max` | ✅ | ✅ opaque `R_1` (type hidden) | coarsened | opaque |
211
+ | `light` | ✅ | left in place | kept | typed |
212
+
213
+ `balanced` keeps coarse structure — the cloud still reads "`ORG_1` hired `P-n2`
214
+ as `ROLE_1` in `LOC_1`" and can reason about it, while no real identity ships.
215
+ **Persons are tokenized in every policy.**
216
+
217
+ ## Swap the model
218
+
219
+ ```bash
220
+ vault-engine models # list local Ollama tags
221
+ vault-engine scrub notes.txt --model qwen3.6:35b-a3b # any local model
222
+ vault-engine scrub notes.txt --provider null # offline, regex only
223
+ ```
224
+
225
+ Built-in providers: `ollama` (default), `openai-compat` (any OpenAI-style
226
+ endpoint — opt-in; ⚠️ sends raw text to that endpoint), `null` (offline). Add
227
+ your own by implementing one method (`complete`) and registering it.
228
+
229
+ ## ⚠️ Security model — read this
230
+
231
+ - **The reverse map (`*.map.json`) *is* the identity.** It's the only thing that
232
+ links tokens back to real people. Keep it local. Never send it to a cloud
233
+ model, never commit it — `.gitignore` excludes `*.map.json` and the CLI warns
234
+ every run. Use `--one-way` to produce no map (irreversible publish).
235
+ - **Detection stays local by default.** Only the sanitized text is meant to
236
+ leave, and only when you send it.
237
+
238
+ ## Threat model & limitations (honest)
239
+
240
+ - LLM detection is **best-effort, not a guarantee** of non-identifiability — a
241
+ model can miss a name or a rare quasi-identifier. It is **not** k-anonymity or
242
+ differential privacy.
243
+ - The critic pass and the risk report reduce and surface residual risk; they
244
+ don't certify its absence. Writing style and domain-unique facts can still
245
+ identify with names removed — use `max` for higher-stakes material.
246
+ - If the model backend is unreachable, the run **degrades to regex-only and
247
+ exits non-zero** (`--allow-degraded` to override) — it will never silently ship
248
+ under-redacted text.
249
+
250
+ ## Protecting code & schemas (`--format markdown`)
251
+
252
+ With `--format markdown` (or `auto`, which switches on at a fenced block),
253
+ anything inside fenced code blocks is preserved verbatim — a JSON reply-schema or
254
+ code sample you include for the model survives untouched while the prose around
255
+ it is scrubbed. Pre-existing placeholder tokens (e.g. `P-7`) pass through
256
+ unchanged.
257
+
258
+ ## Development
259
+
260
+ ```bash
261
+ python -m unittest discover -t . -s tests -v # 59 tests, offline, no model
262
+ python eval/run_eval.py --provider ollama # reproduce the benchmark
263
+ ```
264
+
265
+ Fully offline and deterministic (null/fake providers); every fixture is
266
+ synthetic — no real data lives in this repo.
267
+
268
+ ## License
269
+
270
+ Apache-2.0 © 2026 fishonbike. See [LICENSE](LICENSE) and [NOTICE](NOTICE).