Updated Jul 15, 2026

Recon

Map usernames, repos, and orgs from a target list

Automate GitHub and GitLab dorking from a target list.

Agent

overview

What dorky does

Feed dorky a target list when you need bulk username, repository, and organization matches on GitHub and GitLab without hand-running platform search.

Toggle -u, -r, and -o per category. Restrict to one host with -gh or -gl, cap volume with -max, and use -s when matches must pipe into a secret scanner.

Trickest supplies the managed Recon node with a target list and token files; outputs a folder and a file. Follow with dora or dumpsterdiver on discovered repos. Use enumerepo when valid GitHub usernames already need full public-repo expansion.

source github.com/codingo/dorky

use cases

Where dorky fits

Map an organization's code footprint

Search GitHub and GitLab for repositories and organizations tied to a target list, surfacing code that belongs to the org but lives outside its main account.

Find usernames tied to a target

Enable username search with -u to discover developer accounts associated with an organization, a useful pivot for further OSINT.

Feed repositories into secret scanning

Use -s for simple output so matched repositories pipe straight into a credential scanner and leaked keys in public code get caught.

Scope to one platform

Pass -gh or -gl when you only care about GitHub or GitLab, cutting noise and API spend on the platform you skip.

reference

dorky inputs and flags

12 inputs
NameTypeFlagDescription
inputFILE·List of targets to search for.
maxSTRING-maxMaximum search results per category (default 10).
usernameBOOLEAN-uSearch for username matches.
repositoryBOOLEAN-rSearch for repository names.
organizationBOOLEAN-oSearch for organization names.
github-onlyBOOLEAN-ghSearch only GitHub.
gitlab-onlyBOOLEAN-glSearch only GitLab.
simpleBOOLEAN-sSimple output style for piping to another tool.

Showing key inputs. dorky exposes 12 inputs in total.

Full flag reference (12 inputs)
NameTypeFlagDescription
maxSTRING-maxmaximum search results per category (default 10)
inputFILE·list of targets
simpleBOOLEAN-ssimple output style for piping to another tool
verboseBOOLEAN-venable verbose mode
usernameBOOLEAN-usearch for username matches
repositoryBOOLEAN-rsearch for repository names
github-onlyBOOLEAN-ghsearch only GitHub
gitlab-onlyBOOLEAN-glsearch only GitLab
organizationBOOLEAN-osearch for organization names
clean-input-urlsBOOLEAN-cclean input URLs
github-access-tokenFILE·GitHub access token
gitlab-access-tokenFILE·GitLab access token

example

Run dorky

dorky · command
# dorky: GitHub usernames, repos, and orgs from a target listdorky -u -r -o -gh -max 20 -s targets.txt
sample output
https://github.com/example-orghttps://github.com/example-org/web-frontendhttps://github.com/example-org/payments-apihttps://github.com/example-org/infra-terraformhttps://github.com/example-devhttps://github.com/example-dev/ci-runnershttps://github.com/example-test/docs-sitehttps://github.com/example-app/mobile-client

guidance

Choosing dorky

Use dorky to automate GitHub and GitLab discovery from a target list when you want usernames, repos, or orgs in bulk. Scan found repositories for leaked credentials with dora or dumpsterdiver. Enumerate every public repo for known usernames with enumerepo.

enumerepo

Lists all public repositories for valid GitHub usernames. dorky searches GitHub and GitLab for usernames, repos, and orgs from a target list.

dora

Scans repositories you find for exposed keys. A natural next step after dorky.

faq

dorky questions

GitHub and GitLab. Use -gh or -gl to restrict to one, or leave both flags off to search both by default.

Run dorky yourself

A target list feeds dorky, which finds matching repositories on GitHub and GitLab and passes them to dora so leaked keys land as a queryable output.

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