security

To scan code repositories for PII, run the sanitizer CLI on your project directory to automatically detect and flag sensitive data across all files. It uses configurable blocklists and regex patterns to identify risky content before publication.

In-place PII redaction replaces detected sensitive data with configurable placeholders directly inside your repository files. The sanitizer applies these substitutions based on your custom regex patterns and blocklists to sanitize code bases of any size.

No external dependencies are required to detect sensitive data; the scanner relies solely on the Python standard library. You only need a Python environment to run the CLI, pre-commit hook, and configurable detection rules.

The best way to customize PII detection is by defining specific regex patterns and blocklists in the sanitizer's configurable settings. You can also set skip patterns to exclude certain files or directories from sensitive data scans.

There are no inherent scale limitations for scanning large code bases; the sanitizer is designed for repositories of any size. However, complex custom regex patterns may impact scanning performance, and skip patterns should be configured to exclude irrelevant directories.