feat: add residual PII audit workflow#11
Open
Keerti707 wants to merge 1 commit into
Open
Conversation
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
------Summary-------------------
Adds a lightweight residual PII audit workflow for checking whether redacted JSONL training data still contains sensitive patterns before being used for downstream SFT or DPO training.
This contribution focuses on the privacy-auditing portion of the project requirements and provides a small reusable utility for validating residual-risk after redaction.
------What’s included------------------
JSONL residual PII audit utility
Detection support for:
Risk-level classification
Example redacted dataset
Unit tests with pytest
README usage documentation
pytest configuration through
pyproject.toml------Why this contribution-----------------
The repository requirements explicitly mention:
This PR contributes a focused validation utility around those requirements instead of duplicating broader pipeline/export implementations already being explored in parallel PRs.
-------Verification-------------------
Both commands execute successfully locally.