DETECT-SECRETS(1)

💖 detect-secrets(1) 💖

Okay bestie, welcome to the detect-secrets(1) page from the User Commands corner. The manual name is detect-secrets 1.5.0 — yes, the secret-scanning one. 💅

🌸 NAME 🌸

detect-secrets — manual page for detect-secrets 1.5.0, no cap.

✨ DESCRIPTION ✨

Here’s the usage vibe, literally:

usage: detect-secrets [-h] [-v] [--version] [-C <path>] [-c NUM_CORES]

              {scan,audit} ...

🎀 positional arguments 🎀

• {scan,audit} — the positional choices, bestie. Pick your fighter. 💖
• scan — creates a baseline by scanning a repository for secrets. Iconic behavior, honestly.
• audit — manually assesses a baseline to determine validity of secrets found. It’s giving “let me check if this is actually real.” 🦋

💅 options 💅

• -h, --help — show this help message and exit. The polite escape hatch. ✨
• -v, --verbose — verbose mode. It gets chatty, and we love that for it. 🗣️
• --version — display version information. Main character energy. 👑
• -C <path> — run as if detect-secrets was started in <path>, rather than in the current working directory. Lowkey just pretends it woke up somewhere else. 💫
• -c NUM_CORES, --cores NUM_CORES — specify the number of cores to use for parallel processing. Defaults to using the max cores on the current host. Parallel-processing slay. 🔥

---

Catch you later, bestie — this iconic little page is from detect-secrets 1.5.0, dated August 2025. Mwah! 💖🎀