# Inventory selected paths in an unpacked release

Run the standard-library-only checker with Python 3.10 or newer against one explicit staging directory you control. Keep `selected_paths.json` beside the script.

```text
python check_staged_paths.py /path/to/unpacked-release
```

On Windows, use the installed Python command and quote a directory containing spaces:

```text
py check_staged_paths.py "C:\release staging\site"
```

The checker recursively lists directory entries under that root and reports matching relative filenames as JSON. It does not open artifact file contents, extract archives, contact a service, remove files, or read other home directories. It skips symlinks, junctions, and other reparse points. Use a stable staging directory that is not changing during inspection. Do not run it against a working home directory or assume its output proves what a live server serves.

Exit codes: `0` means no selected filename found in the inspected entries; `1` means at least one selected filename found; `2` means an input error, unreadable entry, or skipped link/reparse point, so review the result as incomplete. With valid input, stdout is JSON and findings contain only relative paths and the selected path group. Errors do not print absolute machine paths or file content. Relative filenames can still be sensitive; review the output before sharing it.

Both case variants and nested release directories match. This checks actual filenames, so URL decoding is irrelevant. The list covers one credential ending and nine configuration endings, using the same paths as the request rules. It does not inventory every tool, inspect archive contents, validate secrets, or determine whether a file belongs in public output. An intentional example can match. Assess each result against your deployment policy, and inspect archives and server routes separately.

Do not treat exit `0` as a secret-scan or exposure certificate. Combine this narrow inventory with your regular secret scanning, build allowlist, and authorized deployed-response checks. See [primary file-location references](../SOURCES.md).
