Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/code-review-secrets-detectionWeb and bug bounty

code-review-secrets-detection

⁨Find leaked secrets in code, git history, and CI. Load on "secrets", "leaked key", a repo/ git history in scope, exposed .git, CI config review, or public-repo OSINT. Signals: API keys, tokens, .env files, private keys, cloud creds, hardcoded passwords.⁩

v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 23 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/code-review-secrets-detection

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
SoAEfSAZsU…DkFU+EBw==The CLI checks the SHA-256 and the signature before it writes a file.
Package10c7f21c…ec32f9f3
10c7f21c9c4c…ad46ec32f9f31 file · ⁦1.3 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/code-review/code-review-secrets-detection@ee0e0c5

When it applies

Any source you can read: an in-scope repo, an exposed .git/ on a web server, public GitHub repos of the org, or CI/CD config. Live secrets are direct, high-impact findings.

Why it works

Secrets get committed and then "removed" — but git keeps history, so they persist in old commits, branches, and stashes. Config/CI files and client bundles also embed keys that ship to users.

Method

  1. Scan history, not just HEAD: trufflehog git file://. --only-verified or gitleaks detect --source . -v — these walk every commit and (trufflehog) verify keys live.
  2. Exposed .git on a target: git-dumper http://target/.git/ out/ then scan the recovered repo.
  3. Org-wide OSINT: GitHub dorks / trufflehog github --org=<org> for public leaks (in scope only).
  4. Client-side & config: grep JS bundles, mobile apps, .env, Dockerfiles, k8s manifests, CI YAML for keys and tokens.
  5. Validate & scope impact: confirm the key works with a read-only call (e.g. aws sts get-caller-identity) — a live, privileged key is the report; a dead one is informational.

Gotchas

  • Report verified/live secrets; example/placeholder keys inflate severity and get closed as N/A.
  • Rotate-awareness: note it may be live now; don't exfiltrate data with it — prove access, stop.
  • Deleted-from-HEAD ≠ gone — always scan full history.

Verify success

A secret that authenticates successfully (minimal proof), with where it lives (commit/file) — don't paste the secret value into reports, reference its location.

References

trufflehog & gitleaks docs; GitHub secret-scanning; OWASP secrets management.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c510c7f21cSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login