Updated Jul 14, 2026

Static Code Analysis

Find leaked secrets across code and Git history

Rule-based secret scanning across text and full Git history.

Agent

overview

What noseyparker does

noseyparker applies detection rules to textual data and full Git history, so API keys and tokens removed from the working tree can still surface. Point it at a file, directory, local repo, or remote clone.

Clone with --git-url, sweep a GitHub user or organization via --github-user and --github-organization, raise parallelism with --jobs, and shape matches with --rules and --ignore.

Trickest runs noseyparker as a managed static-analysis node that accepts a file, directory, or Git source and writes matches to a file and folder. Use it for credential leaks, not for SAST-style injection or logic bugs.

source github.com/praetorian-inc/noseyparker

use cases

Where noseyparker fits

Scan a repository's full history

Clone a Git repo and scan every commit so secrets that were added and later deleted still surface, not only the ones left in the current tree.

Sweep an organization's repos

Point noseyparker at a GitHub user or organization to enumerate and scan every accessible repository through the API in one run.

Tune detection to the codebase

Supply custom rules and a path-based ignore file so the scan matches your secret formats and skips vendored or generated paths.

Catch leaks before release

Scan a build directory or checkout on a schedule so leaked tokens are flagged and routed to an alert before they ship.

reference

noseyparker inputs and flags

18 inputs
NameTypeFlagDescription
input-directoryFOLDER·Scan the specified directory or local Git repository.
input-fileFILE·Scan the specified file.
git-urlSTRING--git-urlClone and scan the Git repository at the specified URL.
github-organizationSTRING--github-organizationClone and scan accessible repositories belonging to the specified GitHub organization.
github-userSTRING--github-userClone and scan accessible repositories belonging to the specified GitHub user.
rulesFILE--rulesUse custom detection rules from the specified file.
ignoreFILE--ignoreUse custom path-based ignore rules from the specified file.
jobsSTRING--jobsUse N parallel scanning jobs (default 10).

Showing key inputs. noseyparker exposes 18 inputs in total.

Full flag reference (18 inputs)
NameTypeFlagDescription
jobsSTRING--jobsUse N parallel scanning jobs (default 10).
colorSTRING--colorEnable or disable colored output (auto, never, always; default auto).
rulesFILE--rulesUse custom detection rules from the specified file.
ignoreFILE--ignoreUse custom path-based ignore rules from the specified file.
git-urlSTRING--git-urlClone and scan the Git repository at the specified URL.
verboseBOOLEAN--verboseEnable verbose output.
progressSTRING--progressEnable or disable progress bars (auto, never, always; default auto).
input-fileFILE·Scan the specified file.
github-userSTRING--github-userClone and scan accessible repositories belonging to the specified GitHub user.
blob-metadataSTRING--blob-metadataChoose which blobs record metadata (all, matching, none; default matching).
max-file-sizeSTRING--max-file-sizeDo not scan files larger than the specified size in MiB (default 100).
git-clone-modeSTRING--git-clone-modeMethod used to clone Git repositories (bare, mirror; default bare).
github-api-urlSTRING--github-api-urlURL to use for GitHub API access (default https://api.github.com/).
snippet-lengthSTRING--snippet-lengthBytes of context to include before and after each match (default 256).
input-directoryFOLDER·Scan the specified directory or local Git repository.
rules-directoryFOLDER--rulesUse custom detection rules from the specified directory.
git-blob-provenanceSTRING--git-blob-provenanceGit commit provenance metadata to collect (first-seen, minimal; default first-seen).
github-organizationSTRING--github-organizationClone and scan accessible repositories belonging to the specified GitHub organization.

example

Run noseyparker

noseyparker · command
# clone a repo, scan its full history, then print the findingsnoseyparker scan --datastore np.db --git-url https://github.com/example/webapp.git --jobs 8noseyparker report --datastore np.db
sample output
Scanned 842.19 MiB from 3,410 blobs in 37 seconds (22.6 MiB/s); 9/9 new matches  Rule                            Distinct Groups   Total Matches ────────────────────────────────────────────────────────────── GitHub Personal Access Token                  2               3 AWS Secret Access Key                         1               1 Generic API Key                               3               4 Slack Token                                   1               1 Run the `report` command next to show finding details.

guidance

Choosing noseyparker

Use noseyparker when you need leaked secrets in source or Git history, including across a GitHub organization. It is a secret scanner, not a SAST engine, so reach for credentials rather than injection or code-quality flaws.

trufflehog

Secret scanner with credential verification. noseyparker emphasizes rule-based scanning across large histories.

gitleaks

Lightweight Git secret scanner. noseyparker adds GitHub org and user sweeps plus parallel jobs for larger runs.

secretfinder

Pulls secrets from JavaScript files specifically. noseyparker scans full repos and history rather than single JS assets.

faq

noseyparker questions

Both. It walks Git history, so a secret that was committed and later deleted is still detected. Point it at a local repo with the directory input, or at a remote one with --git-url.

Run noseyparker yourself

A repository URL feeds noseyparker, which scans the code and full Git history for secrets and writes the matches as a queryable output.

Facts on this page come from the live Trickest tool library.