pii-core
Multi-language PII detection with regex and checksum validation. Pure Python, zero runtime dependencies.
The foundation library that pii-veil (reversible anonymization) and pii-presidio (Microsoft Presidio plugin) build on.
Install
pip install pii-core
What's in v0.1.0
Polish identifiers with regex + checksum validation:
- PESEL (national ID), NIP (tax ID), REGON (business registry — 9 and 14 digit) — weighted-sum checksums.
- Polish IBAN (
PLprefix, mod-97 validated). - Polish ID card (dowód osobisty), passport — regex only (official checksums not yet implemented).
- Polish mobile phone (
+48, optional separators). - Opt-in: KRS court register number (10 digits, no checksum), postal code (
XX-XXX). Excluded fromDEFAULT_DETECTORSbecause their raw patterns collide with ordinary text — pair them with a context-word filter.
Cross-language detectors:
- Email addresses (practical subset, not strict RFC 5322).
- Credit-card numbers (Luhn-validated; bare, dashed, and spaced shapes for Visa / MC / Amex / Discover / Diners).
Multi-country IBAN validator (is_valid_iban) covering ~80 countries via the published SWIFT registry. The PlIbanDetector regex is Polish-only, but the checksum function is general.
Quick usage
from pii_core import DEFAULT_DETECTORS
text = "Mój PESEL: 44051401358, kontakt: jan@example.pl."
for detector in DEFAULT_DETECTORS:
for match in detector.detect(text):
print(f"{match.detector}: {match.value!r} at {match.start}-{match.end}")
from pii_core import is_valid_pesel, is_valid_iban, is_valid_luhn
is_valid_pesel("44051401358") # True
is_valid_iban("DE89370400440532013000") # True
is_valid_luhn("4111111111111111") # True
Opt-in detectors (KRS, postal code) live in pii_core.pl:
from pii_core import DEFAULT_DETECTORS
from pii_core.pl import PlKrsDetector, PlPostalCodeDetector
# Add them only when you have context-word filtering elsewhere in your pipeline.
my_detectors = [*DEFAULT_DETECTORS, PlKrsDetector(), PlPostalCodeDetector()]
API stability
PIIType value strings, detector .name strings, and the order of DEFAULT_DETECTORS are SemVer-stable: downstream consumers persist them in serialized mappings or use them as overlap-resolution priority keys. Internal changes (regex tweaks, helper renames) can churn within minor versions.
Sibling packages
pii-veil— reversible anonymization with persisted mapping and CLI, built onpii-core.pii-presidio— Microsoft Presidio plugin wrappingpii-corerecognizers with optional reversible anonymization.
License
Apache-2.0. See LICENSE.
Metadata
Release files for pii-core 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pii_core-0.1.0.tar.gz | 23.3 kB | Without provenance | Details for pii_core-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pii_core-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for pii_core-0.1.0-py3-none-any.whl |
Total release size: 41.5 kB
Release files / pii_core-0.1.0.tar.gz
| Download URL | pii_core-0.1.0.tar.gz |
|---|---|
| Size | 23.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f27e66c42f4ef4948a1da751c677e214ccc083c322b38b9a4111a194f171c860
|
|
BLAKE2b-256 checksum How to use checksums |
087d79ea3bb93960c7f0cd7f6f4e44480ff9253a8f3be554bac6bb0d8b7a7511
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / pii_core-0.1.0-py3-none-any.whl
| Download URL | pii_core-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
859d6e4fb7c0b3093687b5d09b68e287d39a65fc494b54eada96d07d2523a222
|
|
BLAKE2b-256 checksum How to use checksums |
a02284ac97c58607acb1da8ad255a66277a58103e604d91de9516f20f437777a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for pii-core 0.1.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.