PresidioPresidio
核验标记表示资料完整度,不是产品评分。下列未确认项可能影响选型;请按对应来源逐项确认。The confidence mark describes evidence completeness, not a product score. Unconfirmed items below may affect your choice; check them against the relevant sources.
未确认的信息Information not confirmed
- 仓库 LICENSE 正文未直读到(MIT 依 PyPI 许可字段记录)
- CHANGELOG.md 逐条内容未取到正文
- 支持语言与实体类型的官方完整清单(文档 recognizers 页当日返回 404)
- presidio-anonymizer 与 presidio-image-redaction 各自的版本与发布日期
- Docker 镜像标签与版本的对应关系
- recognizer 语言模型的下载位置与离线打包方式
- 可选 NLP 引擎的完整档位与版本要求
- 遥测/上报是否存在(包索引与文档未声明,本批次未取到反证)
- 大陆网络直连可用性与备案情况(未实测、未检索)
- The repository LICENSE text was not fetched directly (MIT recorded from the PyPI licence field)
- Item-by-item CHANGELOG.md contents, since the file body was not fetched
- The official complete list of supported languages and entity types (the recognizers docs page returned 404)
- Versions and release dates of presidio-anonymizer and presidio-image-redaction individually
- Docker image tag-to-version mapping
- Where recognizer language models are downloaded and how they are packaged offline
- The full set of selectable NLP engine tiers and version requirements
- Whether any telemetry or reporting exists (not declared by the index or docs; no counter-evidence captured)
- Mainland-network direct reachability and filing status (not measured, not searched)
English summaries and interface labels are available. Detailed source notes below are currently in Chinese.
Presidio 是「自己部署的那一层脱敏 SDK」:文档首页把它写成面向 text 与 images 的快速识别与匿名化模块, 三面 API 是 AnalyzerEngine、AnonymizerEngine、Image Redactor,变换算子官方在册 replace / redact / hash / mask / encrypt / keep / custom。它和本大类托管那几份的区别只有一条:文本要不要出你的边界——Presidio 官方口径是在你自己的 部署里完成、支持离线;也因此它的输出没有任何「拦住了多少」的比例含义,官方 analyzer 页甚至专门写着 「Scores are not probabilities」。
Presidio 是「自己部署的那一层脱敏 SDK」:文档首页把它写成面向 text 与 images 的快速识别与匿名化模块, 三面 API 是 AnalyzerEngine、AnonymizerEngine、Image Redactor,变换算子官方在册 replace / redact / hash / mask / encrypt / keep / custom。它和本大类托管那几份的区别只有一条:文本要不要出你的边界——Presidio 官方口径是在你自己的 部署里完成、支持离线;也因此它的输出没有任何「拦住了多少」的比例含义,官方 analyzer 页甚至专门写着 「Scores are not probabilities」。
适合与不适合When to use it, when not to
适合:把个人数据识别与变换插进自己的管线(RAG 入库前、日志落盘前、发给云端模型前)、需要算子级组合与自定义 recognizer、要求文本不出网络边界、需要离线跑完整链路。不适合:要托管控制台与合规交付物;要 text/image 之外的模态 (官方在册面止于这两类);把 score 阈值当合规证明的团队。
中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-11-06
- 出品属地Origin
- 国外出品foreign-made 治理方为社区组织 Data Privacy Stack(文档首页在册),项目源自 Microsoft;本批次未取到面向中国大陆的服务条款或中文文档。Governed by the community organisation Data Privacy Stack (on record on the docs home page), with the project originating at Microsoft; no mainland-facing terms page or Chinese documentation was captured in this pass.
- 国内使用Direct access
- 直连未核验direct unknown 文档站与 PyPI 当日从当前网络取到 200,但仓库页与 raw 路径抓取超时;大陆网络下的可达性与语言模型下载均未实测,故记未知。The docs site and PyPI returned 200 from the current network on the verification date, but the repository page and raw path timed out; mainland-network reachability and language-model download were not measured, so it is recorded as unknown.
- 备案状态CAC filing
- 备案未核验filing unknown:无官方依据,本批次未检索生成式 AI 备案公示,不下「未备案」结论。No official basis; the generative-AI filing registry was not searched in this pass, so no "not filed" conclusion is drawn.
备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准(按批次滚动更新,本站只抄编号不解读);「大陆可直连」是本站从大陆网络直连实测的结果,不是厂商承诺。GitHub 类站点当日实测有波动,口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.
固定坐标系Fixed coordinate system
8 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.
- 模型与开放条件Model & openness
它本身不带生成模型:analyzer 页写明「Predefined recognizers leverage regex, Named Entity Recognition and other types of logic to detect PII in unstructured text.」,识别面由正则、NLP(spaCy / Transformers 类)、规则与校验和组合, 上下文词用来加权 score,自定义 recognizer 有官方 tutorial。可选 NLP 引擎与模型档位的完整清单:本批次未逐条清点。
It carries no generative model of its own: the Analyzer page states "Predefined recognizers leverage regex, Named Entity Recognition and other types of logic to detect PII in unstructured text." — the recognition surface combines regex, NLP (spaCy / Transformers class), rules and checksums, with context words weighting the score, and custom recognizers covered by an official tutorial. The full list of selectable NLP engines and model tiers: not itemised in this pass.
- 运行位置Where it runs
全部跑在你自己的边界内:文档首页的安装口径是 pip 包或 Docker REST API,并写明支持离线使用、数据留在你自己的部署里。 官方未提供托管服务面(未取到该口径)。镜像标签与版本对应关系本批次未逐字核验。
Everything runs inside your own boundary: the docs home page gives the install surface as pip packages or a Docker REST API, and states that offline usage is supported with data staying inside your own deployment. No hosted service surface is offered officially (no such statement captured). Image tags and their version mapping: not verified word for word in this pass.
- 本地文件Local files
它不读你的工作区,只处理你显式交给它的文本与图像,结果在你的进程或你的服务里返回。recognizer 依赖的语言模型文件的 下载位置、缓存路径与离线打包方式:本批次未取到逐字官方说明,记未知。
It does not read your workspace; it processes only the text and images you explicitly hand it, and returns results inside your own process or service. Where the recognizers' language-model files are downloaded and cached, and how they are packaged offline: no word-for-word official statement captured, recorded as unknown.
- 关机后的任务Tasks after shutdown
没有托管后台任务:一次 analyze / anonymize 是一次调用或你自己服务里的一次处理,批量与重试由你的编排层负责。 官方文档目录(Getting Started / Analyzer / Anonymizer / Image Redactor / Samples / API Docs)未出现队列或续跑概念。
There is no hosted background task: one analyze / anonymize call is one invocation, or one pass inside your own service, with batching and retries owned by your orchestration layer. The docs table of contents (Getting Started / Analyzer / Anonymizer / Image Redactor / Samples / API Docs) contains no queue or resume concept.
- 工具与扩展Tools & extensions
三面 API:AnalyzerEngine(识别)、AnonymizerEngine(变换)、Image Redactor(图像遮挡)。变换算子按文档 anonymizer 页 在册:replace、redact、hash、mask、encrypt、keep、custom,经 OperatorConfig 的 type 与 params 配置,多个算子可组合。 MCP 接入方式:官方文档未说明,记未知。
Three API faces: AnalyzerEngine (recognition), AnonymizerEngine (transformation), Image Redactor (image masking). The operators on record from the Anonymizer page are replace, redact, hash, mask, encrypt, keep and custom, configured through OperatorConfig's type and params and combinable. MCP transport support: not described in the official docs, recorded as unknown.
- 上下文与记忆Context & memory
这里的「上下文」是字面机制:recognizer 用上下文词对候选实体加权,因此同一段文本里邻近词会改变结果;文档首页把项目 表述为面向 text and images 的「fast identification and anonymization modules」。它是无状态的一次处理,不存在跨会话记忆, 批量场景的上下文窗口管理属于你自己的调用方。
Here "context" is a literal mechanism: recognizers weight candidate entities with context words, so neighbouring words in the same text change the result; the docs home page describes the project as "fast identification and anonymization modules" for text and images. It is a stateless one-pass handler with no cross-session memory — batch context-window management belongs to your calling code.
- 权限与限制Permissions & limits
许可见 license 字段(MIT,依 PyPI 元数据;LICENSE 正文未直读到)。归属要记两条实测事实:旧址 microsoft.github.io/presidio 当日显示「This page has moved」,中间站 data-privacy-stack.github.io 再 301 到 presidio.dataprivacystack.org,文档首页指认项目由 Data Privacy Stack 治理。数据流向:识别与脱敏在你自己的部署内完成、 支持离线,即文本不必发给第三方。红线口径:analyzer 页原文在册「Scores are not probabilities」,所以 score 阈值 不是检出概率,本站不写检出率、漏检率,也不做任何产品排名;它是否满足某法域的匿名化义务,官方不作法律结论。
See the licence field (MIT, taken from the PyPI licence metadata; the LICENSE text was not read directly). Two measured facts about ownership: the old address microsoft.github.io/presidio displayed "This page has moved" on the verification date, and the intermediate host data-privacy-stack.github.io 301s to presidio.dataprivacystack.org, whose home page states the project is governed by Data Privacy Stack. Data flow: recognition and anonymisation complete inside your own deployment and offline use is supported, meaning text need not be sent to any third party. Red line: the Analyzer page states on record "Scores are not probabilities", so a score threshold is not a detection probability; this site publishes no detection rate, no miss rate and no product rankings. Whether it satisfies an anonymisation obligation under any given law is not a legal conclusion the project makes.
- 适合什么任务Best for
适合:把个人数据识别与变换插进自己的管线(RAG 入库前、日志落盘前、发给云端模型前)、需要算子级定制与自定义 recognizer、要求文本不出自己的网络边界、要把整套东西离线跑。不适合:要托管控制台与合规交付物;要文本与图像之外的 模态(官方在册面止于这两类);把 score 阈值当合规证明的团队。
Fits: inserting personal-data recognition and transformation into your own pipeline (before RAG ingestion, before logs are written, before a call to a hosted model); needing operator-level composition and custom recognizers; requiring text not to leave your network boundary; needing the whole chain to run offline. Not a fit: teams wanting a hosted console and compliance deliverables; modalities beyond text and images (the surface on record stops there); anyone treating a score threshold as proof of compliance.
头号误解Top misconception
- 把 score 当「检出概率」:官方 analyzer 页原文是「Scores are not probabilities」
- 把「算子有七类」当成脱敏覆盖率:算子是可组合动作,官方不给任何命中比例
- 以为仓库还在 microsoft/presidio:旧址已显示 moved、文档首页指认 Data Privacy Stack 治理
证据来源Evidence sources
最近核验记录Latest recorded check 2026-11-06,内容更新日content updated on 2026-11-06。单项复核范围见正文或来源说明,不代表所有字段在同一天重新核验。See the text or source notes for item-specific scope; this does not mean every field was rechecked on that date.
| 类型Type | 名称Name | 链接Link |
|---|---|---|
| docs | Presidio · 文档首页(新址定位句、pip/Docker REST 与离线口径、Data Privacy Stack 治理、目录与 CHANGELOG 链接;直读 200,2026-11-06)Presidio · docs home page (new address, positioning sentence, pip/Docker REST and offline statements, Data Privacy Stack governance, table of contents and CHANGELOG link; direct-fetched 200, 2026-11-06) | https://presidio.dataprivacystack.org/ |
| migration | Presidio · 旧文档址(「This page has moved」迁移事实;直读 200,2026-11-06)Presidio · old docs address (the "This page has moved" migration fact; direct-fetched 200, 2026-11-06) | https://microsoft.github.io/presidio/ |
| docs | Presidio · 文档 Analyzer(recognizer 逻辑原文、「Scores are not probabilities」、上下文词加权与自定义 recognizer;直读 200,2026-11-06)Presidio · docs Analyzer (recognizer logic wording, "Scores are not probabilities", context-word weighting and custom recognizers; direct-fetched 200, 2026-11-06) | https://presidio.dataprivacystack.org/analyzer/ |
| docs | Presidio · 文档 Anonymizer(算子 replace/redact/hash/mask/encrypt/keep/custom 与 OperatorConfig;直读 200,2026-11-06)Presidio · docs Anonymizer (operators replace/redact/hash/mask/encrypt/keep/custom and OperatorConfig; direct-fetched 200, 2026-11-06) | https://presidio.dataprivacystack.org/anonymizer/ |
| docs | presidio-analyzer · PyPI 项目页(2.2.366、许可字段 MIT、摘要与 Home 指认的仓库地址;直读 200,2026-11-06)presidio-analyzer · PyPI project page (2.2.366, licence field MIT, summary and the repository address named as Home; direct-fetched 200, 2026-11-06) | https://pypi.org/project/presidio-analyzer/ |
| changelog | presidio-analyzer · PyPI 发布历史(2.2.366 至 2.2.361 的日期序列;直读 200,2026-11-06)presidio-analyzer · PyPI release history (the 2.2.366 down to 2.2.361 date sequence; direct-fetched 200, 2026-11-06) | https://pypi.org/project/presidio-analyzer/#history |
| repo | data-privacy-stack/presidio · 仓库页(文档首页指认的仓库位置;本批次直抓失败,未取到正文,仅登记链接关系,2026-11-06)data-privacy-stack/presidio · repository page (the location the docs home page points at; direct fetch failed in this pass, no body captured, only the link relation recorded, 2026-11-06) | https://github.com/data-privacy-stack/presidio |
| changelog | data-privacy-stack/presidio · CHANGELOG(文档首页指认的变更文件;本批次直抓失败,未取到正文,2026-11-06)data-privacy-stack/presidio · CHANGELOG (the change file named by the docs home page; direct fetch failed in this pass, no body captured, 2026-11-06) | https://github.com/data-privacy-stack/presidio/blob/main/CHANGELOG.md |
官方口径与未核到项Official record and unverified items
本站未做端到端实测:没有安装并调用过 AnalyzerEngine/AnonymizerEngine,没有跑过任何语料来测命中效果, 不产出检出率、漏检率、精度或任何排名,也不清点官方 recognizer 数量。本档案只组织文档首页、Analyzer/Anonymizer 两个 文档页、PyPI 项目页与发布历史在册的说法。
实测建议(四条):
- 自定义 recognizer 的接入成本(官方 tutorial 在册,实际改动量要自己试)
- 离线部署时语言模型的获取路径(官方文档未逐字说明下载与缓存位置)
- 算子组合的可逆性与审计留痕(replace 与 encrypt 混用后的还原边界)
- 换非英语语言时的实体覆盖面差异(本站不给出比例结论,只验证机制是否可用)
This site has not run it end to end: AnalyzerEngine/AnonymizerEngine were never installed or called, no corpus was run to test hit behaviour, so no detection rate, miss rate, precision or ranking is produced, and the number of official recognizers is not tallied. This archive only organises statements on record at the docs home page, the Analyzer and Anonymizer pages, the PyPI project page and its release history.
Suggested measurements (four):
- The real cost of wiring a custom recognizer (the tutorial is on record; the amount of change is yours to test)
- How language models are obtained in an offline deployment (download and cache locations are not spelled out officially)
- Reversibility and audit trail of combined operators (what the restore boundary looks like when replace meets encrypt)
- Entity coverage differences outside English (this site draws no ratio conclusion — only whether the mechanism works)
变更记录说明
本对象有可核验的变更记录,但不在仓库页上:PyPI 发布历史在册(presidio-analyzer 2.2.366 发布于 2026-10-27、 2.2.365 于 2026-10-25、2.2.364 于 2026-07-22、2.2.363 于 2026-06-28、2.2.362 于 2026-03-15、2.2.361 于 2026-02-12)。 文档首页另指认 CHANGELOG.md 位于 github.com/data-privacy-stack/presidio,本批次该仓库页与 raw 路径均抓取超时, 未取到正文——所以变更内容口径以包索引日期为准,逐条内容进 unknowns。按发布密度(近 30 天内有版本)判 lifecycle active。
能力边界
- 模态面:官方在册只有文本与图像两条(image redaction 是独立组件)。
- 判定面:输出是候选实体与 score,官方明确 score 不是概率;把它读成任何百分比都是越界。
- 变换面:算子是动作(遮、替、哈希、加密、保留、自定义),不承诺「脱敏后不可逆推」这类结论,那是你选算子与密钥管理的责任。
- 合规面:它不产出法律结论;GDPR/个保法意义上的匿名化是否成立,取决于你的整体处理方案,而不是这一个 SDK。
部署建议
- 先定边界:如果「文本不出内网」是硬约束,本档案这条线是唯一可选项;否则才需要比较托管方案。
- 装两个包(analyzer 与 anonymizer),先用官方 tutorial 跑一遍 replace 与 mask,再决定要不要自定义 recognizer。
- 需要服务化时用官方 Docker REST 路径,但把镜像标签与版本钉住——本批次未取到标签对应关系。
- 记录配置而非结果分数:把 recognizer 集、上下文词与算子参数进版本控制;把 score 阈值写进文档时要同时写明官方那句 「Scores are not probabilities」。
相关条目Related entries
- NightfallNightfall同是「进模型前处理个人数据」,差别在谁执行:那份是托管 API 与算子配置,本档案全部跑在你自己边界内。Also "handle personal data before it reaches the model", but the difference is who executes: that archive is a hosted API with configured operators, this one runs entirely inside your own boundary.
- GitGuardianGitGuardian管的是另一类敏感物:凭据与密钥;两者常在同一条管线上前后串起来,本站不排名。Covers a different class of sensitive material — credentials and secrets; the two are often chained on the same pipeline, and this site does not rank them.
- Microsoft Agent FrameworkMicrosoft Agent Framework编排侧:脱敏算子要接进 agent 的输入输出管道时,落点在编排框架那一层。The orchestration side: when redaction operators must sit in an agent's input/output path, the landing point is the agent framework layer.
本页由This page is generated from the ai-handbook 数据层生成(CC BY 4.0)。data layer (CC BY 4.0).
方法论与坐标系定义见仓库内For the methodology and coordinate definitions, see METHODOLOGY.md.