You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Epic] D1-4 · Data audit, PII/secret detection and ingestion #851
Data audit, PII/secret detection and ingestion problems that let the audit call data clean that it never scanned.
How to work on it
Every sub-issue below is independent and can be claimed on its own — see CONTRIBUTING.md, Finding Work: Issues and the Project Board. Progress shows in the sub-issue list and in the project's Sub-issues progress field.
Done when
Every sub-issue is closed (fixed, or 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.
Activity
forgelm auditverifies redaction and catches what masking missed, but the audit runs the same regexes with no normalisation and flags none of the 75 leaked… (CR-A11-019) #393forgelm ingest, which cannot read JSONL: exit 0, empty output, false 'no credentials detected' note, and the next au… (CR-A11-021) #394forgelm auditflags chosen == rejected preference rows (with fabricated sample output); no such check exists (CR-MISC-006) #397