xenmask
Reversible PHI/PII de-identification round-trip for agentic LLM pipelines.
Mask sensitive fields to typed, referentially-consistent surrogate tokens before they reach an LLM; unmask the model's output afterward — with the round-trip enforced as a verifiable invariant (an unmapped token in the output is an error, never shipped).
⚠️ 0.0.0 placeholder. This name is reserved while the v1 API is under active design. Not yet functional. Follow the repo for the first real release.
Why
Static de-identification destroys the linkage you need to keep working. xenmask
de-identifies reversibly and locally (no SaaS, no data egress), so you can run
agentic intelligence over clinical/casework data and still get real answers back.
Licensed under Apache-2.0.
1 maintainer
Metadata
1 maintainer
Release files for xenmask 0.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| xenmask-0.0.0-py3-none-any.whl | Python 3 | none | any | Details for xenmask-0.0.0-py3-none-any.whl |
Release files / xenmask-0.0.0-py3-none-any.whl
| Download URL | xenmask-0.0.0-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b0825a3b0a0bf773ad6b4387152f1acf4044c4ba9fbfef288291dbcd90d987be
|
|
BLAKE2b-256 checksum How to use checksums |
41e07c553c16b542ee194b9a40a38ee5d4c40d475a96a7495edb4149294d3294
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for xenmask 0.0.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.
