PiiTagger
Flags endpoints that accept personally identifiable information (PII) or other sensitive personal data. These endpoints are prime review targets for data exposure, broken object-level authorization, and sensitive-data logging — knowing which routes touch PII lets a reviewer (or an AI consumer) prioritize accordingly.
Constants
Weaker individually (a single one shows up in countless benign forms), so require at least two before tagging.
Unambiguous, high-signal identifiers. A single one is enough to flag the endpoint because these names rarely appear outside a PII context.
Single, unambiguous tokens. Matched anywhere in a (normalized) param
name so compound names like userSsn, customer_cvv, or
applicantPassport are caught without enumerating every prefix.