How to use Local Multi-File Secret-Pattern Scanner
- Supply the text files to scan and extra literal terms, one per line using the supported input described beside the controls.
- Review the selected options and the declared scope, then run the local secret pattern scanner.
- Read the result and unresolved findings before downloading or sharing a report. The original input is not changed.
Example: Local Multi-File Secret-Pattern Scanner
Review selected text files for documented credential patterns and selected user terms. This example uses synthetic public data and the named local fixture files.
Options
- Text files
- Select files within the shown count and byte limits. Binary data, archives and OCR need another workflow.
- Literal terms
- Optional entered terms are matched literally and are omitted from results. They do not become regular expressions.
Supported inputs and limits
Where your input is processed
This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.
A finding is a review location
The report identifies a file, line and pattern class without displaying the matched value or surrounding source. Fixed patterns can produce false positives, while unlisted or altered secrets can be missed. Review findings in your own files and do not treat a clear report as proof that a collection contains no secrets.
Questions about Local Multi-File Secret-Pattern Scanner
Are secret values printed?
No. Findings omit values and source snippets.
Does zero mean no secrets exist?
No. It means no supported pattern or entered literal term was found in the selected supported text.
Does it test whether a token works?
No. It makes no authentication or network requests.