# ayoubfathi/leaky-paths

A collection of special paths linked to common sensitive APIs, devops internals, frameworks conf, known misconfigurations, juicy APIs ..etc. It could be used as a part of web content discovery, to scan passively for high-quality endpoints and quick-wins.

Repository: https://github.com/ayoubfathi/leaky-paths
Canonical: https://ross.abutalabs.com/products/leaky-paths
License Family: other
Topics: fuzzing, recon, bugbounty, pentest, security, security-tools, nuclei, dirsearch, ffuf, dirbuster, appsec, penetration-testing, redteam, redteaming, wordlist, axiom, meg, subfinder, wayback-machine, hacktoberfest
Last push: 2026-04-03T09:57:40+00:00

## Health v2 (maintenance only)
Score: 66/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 75, release rhythm 35, longevity 100
- inputs: {"age_days": 2056, "days_push": 152, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1193, forks 171 (observed 2026-08-28T04:03:56.468533+00:00)

## What it is
A curated wordlist of special web paths linked to sensitive APIs, devops internals, framework configs, and known misconfigurations. It is designed for web content discovery to passively scan for high-value endpoints and quick wins.

## Use cases
- find leaked sensitive endpoints on a target during a pentest
- scan subdomains for quick wins in a bug bounty program
- use with ffuf or dirsearch for targeted content discovery
- feed paths into nuclei templates for misconfiguration checks
- enrich external attack surface scanning with high-quality endpoints
- discover hidden or verbose API endpoints on web servers

## When to choose
- you need a short, high-signal wordlist of juicy paths rather than a huge brute-force list
- you are doing recon or bug bounty hunting and want fast quick-win checks
- you want community-maintained paths for modern tech stacks and infrastructure

## When to avoid
- you need comprehensive active-scanning wordlists covering broad directory brute-forcing
- you want CVE-specific exploit paths, since the list intentionally de-emphasizes CVEs
- you need a tool rather than a wordlist - pair it with ffuf, dirsearch, or meg

## Facets
- artifact type: dataset
- maturity: active
- function: security, penetration-testing, web-scraping, fuzzing
- domain: security, penetration-testing, developer-tools, apis
- platform: cli, cross-platform
- tags: wordlist, bugbounty, recon, content-discovery, dirsearch, ffuf, nuclei, redteam, appsec

## Member repositories
- ayoubfathi/leaky-paths (main) score 66

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:56.468533+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:22:13.182308+00:00, confidence not recorded.
  - readme: https://github.com/ayoubfathi/leaky-paths (fetched 2026-08-28T04:03:56.468533+00:00, sha 8feae8facc47)
- Data as of 2026-08-30T08:39:29.467469+00:00.