spanforge 2.0.1__tar.gz → 2.0.2__tar.gz

{spanforge-2.0.1 → spanforge-2.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spanforge
-Version: 2.0.1
+Version: 2.0.2
 Summary: SpanForge — AI lifecycle and governance platform (RFC-0001 SPANFORGE)
 Project-URL: Homepage, https://github.com/veerarag1973/spanforge
 Project-URL: Documentation, https://github.com/veerarag1973/spanforge/blob/main/docs/index.md

{spanforge-2.0.1 → spanforge-2.0.2}/docs/api/redact.md

@@ -183,7 +183,7 @@ The original event is **not** mutated.
 
 ## Module-level functions
 
-### `contains_pii(event: Event, *, scan_raw: bool = False) -> bool`
+### `contains_pii(event: Event, *, scan_raw: bool = True) -> bool`
 
 Return `True` if any payload value is a `Redactable` with
 `sensitivity >= Sensitivity.PII`.
@@ -193,13 +193,13 @@ Return `True` if any payload value is a `Redactable` with
 | Parameter | Type | Description |
 |-----------|------|-------------|
 | `event` | `Event` | The event to inspect. |
-| `scan_raw` | `bool` | When `True`, also run regex-based PII scanning on payload strings (via `scan_payload()`), not just check for `Redactable` wrappers. Default `False`. |
+| `scan_raw` | `bool` | When `True` (default), also run regex-based PII scanning on payload strings (via `scan_payload()`), not just check for `Redactable` wrappers. Pass `False` to check `Redactable` wrappers only. |
 
 **Returns:** `bool`
 
 ---
 
-### `assert_redacted(event: Event, context: str = "", *, scan_raw: bool = False) -> None`
+### `assert_redacted(event: Event, context: str = "", *, scan_raw: bool = True) -> None`
 
 Raise `PIINotRedactedError` if the event still contains unredacted PII or PHI.
 
@@ -211,7 +211,7 @@ Use this as a guardrail before exporting events.
 |-----------|------|-------------|
 | `event` | `Event` | The event to check. |
 | `context` | `str` | Optional context string embedded in the exception message. |
-| `scan_raw` | `bool` | When `True`, also run regex-based PII scanning. Default `False`. |
+| `scan_raw` | `bool` | When `True` (default), also run regex-based PII scanning. Pass `False` to check `Redactable` wrappers only. |
 
 **Raises:** `PIINotRedactedError` — if any `Redactable` PII/PHI values or raw PII patterns remain in the payload.
 
@@ -287,7 +287,7 @@ Scan a payload dictionary for PII using regex detectors.
 Walks the entire payload recursively (up to `max_depth`), testing every string
 value against the built-in pattern set plus any caller-supplied patterns.
 
-**Built-in detectors:** `email`, `phone`, `ssn` (with SSA range validation via `_is_valid_ssn`), `credit_card` (with Luhn validation), `ip_address`, `uk_national_insurance`, `date_of_birth` (with calendar validation via `_is_valid_date`), `address`.
+**Built-in detectors:** `email`, `phone`, `ssn` (with SSA range validation via `_is_valid_ssn`), `credit_card` (with Luhn validation), `ip_address`, `uk_national_insurance`, `date_of_birth` (global formats — ISO, US MDY, day-first DMY, written-month DMY/MDY — with calendar validation via `_is_valid_date`), `address`.
 
 **Args:**
 

{spanforge-2.0.1 → spanforge-2.0.2}/docs/changelog.md

@@ -6,7 +6,7 @@ this project adheres to [Semantic Versioning](https://semver.org/).
 
 ---
 
-## 2.0.1 — 2026-04-14
+## 2.0.2 — 2026-04-14
 
 **Compliance Integration Hardening & CostGuard Enhancements**
 
@@ -108,11 +108,18 @@ this project adheres to [Semantic Versioning](https://semver.org/).
 
 ### Added — Extended PII Pattern Coverage
 
-- **`date_of_birth` pattern** — detects dates of birth in `MM/DD/YYYY`,
-  `MM-DD-YYYY`, `YYYY-MM-DD`, and `YYYY/MM/DD` formats (centuries 1900–2099).
+- **`date_of_birth` pattern** — detects dates of birth across all major global
+  formats (centuries 1900–2099):
+  - ISO / year-first: `YYYY-MM-DD`, `YYYY/MM/DD`, `YYYY.MM.DD`
+  - US month-first: `MM/DD/YYYY`, `MM-DD-YYYY`, `MM.DD.YYYY`
+  - Day-first (UK, EU, Germany, Asia, Australia, Latin America): `DD/MM/YYYY`,
+    `DD-MM-YYYY`, `DD.MM.YYYY`
+  - Written day-first: `15 Jan 2000`, `15-Jan-2000`, `15 January 2000`
+  - Written month-first: `Jan 15, 2000`, `January 15 2000`
+
   Secondary calendar validation via `_is_valid_date()` rejects impossible dates
-  (e.g. `02/30/1990`, `13/01/1990`).  Mapped to sensitivity `"high"`.
-- **`address` pattern** — detects US street addresses (`<number> <name> <suffix>`)
+  (e.g. `02/30/1990`, `31/04/1990`).  Mapped to sensitivity `"high"`.
+- **`address` pattern** — detects street addresses (`<number> <name> <suffix>`)
   with a curated suffix list (Street/St, Avenue/Ave, Road/Rd, Boulevard/Blvd,
   Drive/Dr, Lane/Ln, Court/Ct, Way, Place/Pl, Circle/Cir, Trail/Trl,
   Terrace/Ter, Parkway/Pkwy, Highway/Hwy, Route/Rte).  Mapped to sensitivity
@@ -122,7 +129,8 @@ this project adheres to [Semantic Versioning](https://semver.org/).
   `900–999` (ITIN-reserved), group `00`, and serial `0000`, eliminating the
   most common false-positive ranges.
 - **`_is_valid_date(date_str)`** — calendar correctness validator applied
-  post-regex to every `date_of_birth` match.  Delegates to
+  post-regex to every `date_of_birth` match.  Tries 15 `strptime` format
+  strings covering all numeric and written-month orderings; delegates to
   `datetime.strptime` for accurate month-length and leap-year enforcement.
 - Both validators follow the same pattern as existing `_luhn_check()` and
   `_verhoeff_check()` — applied inside `scan_payload._walk()` after the regex

{spanforge-2.0.1 → spanforge-2.0.2}/docs/cli.md

@@ -794,7 +794,8 @@ result = scan_payload(event.payload, extra_patterns=DPDP_PATTERNS)
 ```
 
 Built-in types: `email`, `phone`, `ssn`, `credit_card`, `ip_address`,
-`uk_national_insurance`, `date_of_birth`, `address`. DPDP add-on types: `aadhaar` (high), `pan` (high).
+`uk_national_insurance`, `date_of_birth` (global formats: ISO, US, day-first
+DMY, written-month), `address`. DPDP add-on types: `aadhaar` (high), `pan` (high).
 
 ---
 

{spanforge-2.0.1 → spanforge-2.0.2}/docs/quickstart.md

@@ -181,9 +181,12 @@ for hit in result.hits:
 # address: home (sensitivity=medium)
 ```
 
-Calendar-invalid dates (e.g. `02/30/1990`) and SSNs in reserved ranges
-(area `000`, `666`, `900–999`) are automatically filtered out to reduce false
-positives.
+The `date_of_birth` detector recognises all major global formats: ISO
+(`YYYY-MM-DD`, `YYYY.MM.DD`), US month-first (`MM/DD/YYYY`, `MM.DD.YYYY`),
+day-first (UK/EU/Asia: `DD/MM/YYYY`, `DD.MM.YYYY`), and written-month forms
+(`15 Jan 2000`, `January 15, 2000`).  Calendar-invalid dates (e.g.
+`02/30/1990`, `31/04/1990`) and SSNs in reserved ranges (area `000`, `666`,
+`900–999`) are automatically filtered out to reduce false positives.
 
 ## Exporting events
 

{spanforge-2.0.1 → spanforge-2.0.2}/pyproject.toml

@@ -7,7 +7,7 @@ build-backend = "hatchling.build"
 # ---------------------------------------------------------------------------
 [project]
 name = "spanforge"
-version = "2.0.1"
+version = "2.0.2"
 description = "SpanForge — AI lifecycle and governance platform (RFC-0001 SPANFORGE)"
 readme = "README.md"
 license = { text = "MIT" }

{spanforge-2.0.1 → spanforge-2.0.2}/src/spanforge/__init__.py

@@ -399,7 +399,7 @@ from spanforge.explain import (
 )
 from spanforge.namespaces.consent import ConsentPayload
 from spanforge.namespaces.hitl import HITLPayload
-__version__: str = "2.0.1"
+__version__: str = "2.0.2"
 #: RFC-0001 SPANFORGE conformance profile label.
 from typing import Final as _Final
 CONFORMANCE_PROFILE: _Final[str] = "SPANFORGE-Enterprise-2.0"

{spanforge-2.0.1 → spanforge-2.0.2}/src/spanforge/redact.py

@@ -586,12 +586,32 @@ _PII_PATTERNS: Final[dict[str, re.Pattern[str]]] = {
         r"\b[A-CEGHJ-PR-TW-Z]{2}\s?\d{2}\s?\d{2}\s?\d{2}\s?[A-D]\b",
         re.IGNORECASE,
     ),
-    # Date of birth — MM/DD/YYYY, MM-DD-YYYY, YYYY-MM-DD, YYYY/MM/DD
-    # _is_valid_date() provides secondary calendar correctness check.
+    # Date of birth — numeric (/, -, .) and written-month forms covering
+    # ISO/YMD, US MDY, day-first DMY (Europe/Asia/Australia/etc.), and
+    # long/short written-month variants.  Years restricted to 19xx–20xx to
+    # limit false positives.  _is_valid_date() provides secondary calendar-
+    # correctness check (leap-year rules, month lengths, etc.).
     "date_of_birth": re.compile(
-        r"\b(?:0?[1-9]|1[0-2])[/\-](?:0?[1-9]|[12]\d|3[01])[/\-](?:19|20)\d{2}\b"
+        # ISO / YMD: YYYY-MM-DD, YYYY/MM/DD, YYYY.MM.DD
+        r"\b(?:19|20)\d{2}[-/.](?:0?[1-9]|1[0-2])[-/.](?:0?[1-9]|[12]\d|3[01])\b"
         r"|"
-        r"\b(?:19|20)\d{2}[/\-](?:0?[1-9]|1[0-2])[/\-](?:0?[1-9]|[12]\d|3[01])\b"
+        # US MDY: MM/DD/YYYY, MM-DD-YYYY, MM.DD.YYYY
+        r"\b(?:0?[1-9]|1[0-2])[-/.](?:0?[1-9]|[12]\d|3[01])[-/.](?:19|20)\d{2}\b"
+        r"|"
+        # Day-first DMY: DD/MM/YYYY, DD-MM-YYYY, DD.MM.YYYY (UK, EU, Asia, etc.)
+        r"\b(?:0?[1-9]|[12]\d|3[01])[-/.](?:0?[1-9]|1[0-2])[-/.](?:19|20)\d{2}\b"
+        r"|"
+        # Written DMY: "15 Jan 2000", "15-Jan-2000", "15 January 2000"
+        r"\b(?:0?[1-9]|[12]\d|3[01])[\s\-]"
+        r"(?:Jan(?:uary)?|Feb(?:ruary)?|Mar(?:ch)?|Apr(?:il)?|May|Jun(?:e)?"
+        r"|Jul(?:y)?|Aug(?:ust)?|Sep(?:tember)?|Oct(?:ober)?|Nov(?:ember)?|Dec(?:ember)?)"
+        r"[\s\-](?:19|20)\d{2}\b"
+        r"|"
+        # Written MDY: "Jan 15, 2000", "January 15 2000"
+        r"\b(?:Jan(?:uary)?|Feb(?:ruary)?|Mar(?:ch)?|Apr(?:il)?|May|Jun(?:e)?"
+        r"|Jul(?:y)?|Aug(?:ust)?|Sep(?:tember)?|Oct(?:ober)?|Nov(?:ember)?|Dec(?:ember)?)"
+        r"\s+(?:0?[1-9]|[12]\d|3[01]),?\s+(?:19|20)\d{2}\b",
+        re.IGNORECASE,
     ),
     # Street address — house number + street name + recognised suffix
     "address": re.compile(
@@ -757,23 +777,44 @@ def _is_valid_ssn(ssn_str: str) -> bool:
 def _is_valid_date(date_str: str) -> bool:
     """Return ``True`` if *date_str* is a valid calendar date.
 
-    Accepts the four formats produced by the ``"date_of_birth"`` regex in
-    :data:`_PII_PATTERNS`:
+    Accepts all numeric and written-month formats produced by the
+    ``"date_of_birth"`` regex in :data:`_PII_PATTERNS`.
 
-    * ``MM/DD/YYYY`` and ``MM-DD-YYYY``
-    * ``YYYY/MM/DD`` and ``YYYY-MM-DD``
+    Numeric formats (separators ``/``, ``-``, ``.``):
+
+    * ``YYYY/MM/DD``, ``YYYY-MM-DD``, ``YYYY.MM.DD`` — ISO / year-first
+    * ``MM/DD/YYYY``, ``MM-DD-YYYY``, ``MM.DD.YYYY`` — US month-first
+    * ``DD/MM/YYYY``, ``DD-MM-YYYY``, ``DD.MM.YYYY`` — day-first (Europe,
+      Asia, Australia, Latin America, etc.)
+
+    Written-month formats:
+
+    * ``DD Mon YYYY``, ``DD-Mon-YYYY``, ``DD Month YYYY`` (e.g. 15 Jan 2000)
+    * ``Mon DD, YYYY``, ``Mon DD YYYY``, ``Month DD, YYYY`` (e.g. Jan 15, 2000)
 
     Delegates to :func:`datetime.datetime.strptime` so leap-year rules and
-    month-length limits are enforced (e.g. ``02/30/2000`` is rejected).
+    month-length limits are enforced (e.g. ``31/04/1990`` is rejected).
 
     Args:
         date_str: Raw match string from the ``"date_of_birth"`` regex.
 
     Returns:
-        ``True`` if the string represents a real calendar date; ``False``
-        if no known format matches or the date is not calendar-valid.
+        ``True`` if the string represents a real calendar date in any of the
+        recognised formats; ``False`` otherwise.
     """
-    for fmt in ("%m/%d/%Y", "%m-%d-%Y", "%Y/%m/%d", "%Y-%m-%d"):
+    _FORMATS = (
+        # ISO / YMD
+        "%Y/%m/%d", "%Y-%m-%d", "%Y.%m.%d",
+        # US MDY
+        "%m/%d/%Y", "%m-%d-%Y", "%m.%d.%Y",
+        # Day-first DMY (Europe, Asia, Australia, Latin America, etc.)
+        "%d/%m/%Y", "%d-%m-%Y", "%d.%m.%Y",
+        # Written DMY: "15 Jan 2000", "15-Jan-2000", "15 January 2000"
+        "%d %b %Y", "%d-%b-%Y", "%d %B %Y", "%d-%B-%Y",
+        # Written MDY: "Jan 15, 2000", "Jan 15 2000", "January 15, 2000"
+        "%b %d, %Y", "%b %d %Y", "%B %d, %Y", "%B %d %Y",
+    )
+    for fmt in _FORMATS:
         try:
             datetime.datetime.strptime(date_str.strip(), fmt)
             return True

{spanforge-2.0.1 → spanforge-2.0.2}/tests/test_phase11_security.py

@@ -252,4 +252,4 @@ class TestConfigureIntegration:
 
     def test_version_is_1_0_0(self):
         """spanforge.__version__ must match the current release."""
-        assert spanforge.__version__ == "2.0.0"
+        assert spanforge.__version__ == "2.0.2"