Repository navigation
Data-audit methods: Presidio documentation URL embedded in error messages (outdated) (TECH-T06-004) #491
Description
Wave 2 · theme D2-7: Next-release technology updates · highest severity Next release · 1 finding(s) · effort not estimated
Summary
The actionable hint in two ValueError messages leads to a 404. The repository link in data_audit.md:405 still resolves through a redirect.
Primary finding
TECH-T06-004 — Data-audit methods: Presidio documentation URL embedded in error messages (outdated)
severity Next release
Item. Presidio documentation URL embedded in error messages · verdict: outdated · urgency: Next release
State in ForgeLM. forgelm/data_audit/_pii_ml.py:109 and :178 point operators to https://microsoft.github.io/presidio/analyzer/languages/. docs/guides/data_audit.md:405 links github.com/microsoft/presidio.
State of the ecosystem on 2026-10-01. On 2026-10-01 the old URL returned HTTP 404 (arbiter re-fetch), and https://presidio.dataprivacystack.org/analyzer/languages/ returned 200. The GitHub repository is now data-privacy-stack/presidio.
Impact. The actionable hint in two ValueError messages leads to a 404. The repository link in data_audit.md:405 still resolves through a redirect.
Recommendation. Change both URLs to https://presidio.dataprivacystack.org/analyzer/languages/ and update the repository link.
Sources.
- Old Presidio languages page (HTTP 404 on 2026-10-01) (2026-10-01T16:15:15Z)
- Presidio docs: PII detection in different languages (new location, HTTP 200) (2026-10-01T16:15:15Z)
- GitHub API: microsoft/presidio -> data-privacy-stack/presidio (2026-10-01T13:59:01Z)
Acceptance criteria
- Each statement is re-checked against the code at fix time.
- Documentation listed above is corrected in English and in its Turkish mirror in the same PR.
- Every finding in this issue is resolved or explicitly closed with a reason.
Found by the October 2026 ForgeLM code and documentation review against commit cab2947. Code links point at that commit; line numbers may have moved since. Finding IDs (CR-…, DOC-…, TECH-…) are stable references for this backlog.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
cemililik commentedon Oct 11, 2026
Where to start
Thanks for taking a look. Please confirm the issue is unassigned and comment before starting so work does not overlap.
Start with these files on
development:Replace the dead language-help URL in both actionable error paths with https://presidio.dataprivacystack.org/analyzer/languages/ and update related guide links. Exercise unsupported-language and unsupported-analyzer errors with mocks, asserting the exception remains actionable and points to the current documentation. Tests must not fetch the URL or install spaCy models.
Old help URL returned 404; the current primary documentation returned 200. Static source evidence plus HTTP check, not an ML-model execution.
Run the focused tests:
Run these guards/checks as applicable to the changed files:
If user-facing documentation changes, update the existing Turkish mirror in the same PR; keep commands, code and terminal output in English and structurally aligned. English-only contributor standards need no new mirror.
Open the PR against
developmentwithFixes #491once every finding is resolved or explicitly closed with a reason; useRefs #491for partial work and list the resolved finding IDs.fix: point Presidio links at the live docs and repository
fix: point Presidio links at the live docs and repository (HodeTech#936)
fix: point Presidio links at the live docs and repository (HodeTech#936)