# Gitrecon | OSINT Tool To Get Information From A Github Profile

**URL:** <https://onehack.st/t/gitrecon-osint-tool-to-get-information-from-a-github-profile/176870>\
**Category:** Tools & Scripts\
**Tags:** piracy, freebies, business, email, tips-tricks\
**Created:** [March 28, 2021, 2:56pm UTC](https://onehack.st/t/gitrecon-osint-tool-to-get-information-from-a-github-profile/176870 "2021-03-28T14:56:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shayla](https://onehack.st/user_avatar/onehack.st/shayla/32/174870_2.png) [@Shayla](https://onehack.st/u/Shayla)\
**Post date:** [March 28, 2021, 2:56pm UTC](https://onehack.st/t/gitrecon-osint-tool-to-get-information-from-a-github-profile/176870/1 "2021-03-28T14:56:07Z")

</div>

![image](https://onehack.st/uploads/default/original/3X/f/0/f0f2feb00c8d4c01bcd3a65a11c1891fe6440084.png)

OSINT tool to get information from a github profile and find GitHub user’s email addresses leaked on commits.

**How does this work?**

GitHub uses the email address associated with a GitHub account to link commits and other activity to a GitHub profile. When a user makes commits to public repos their email address is usually published in the commit and becomes publicly accessible, if you know where to look.

GitHub provide some [instructions](https://help.github.com/articles/setting-your-email-in-git/) on how to prevent this from happening, but it seems that most GitHub users either don’t know or don’t care that their email address may be exposed.

Finding a GitHub user’s email address is often as simple as looking at their [recent events](https://developer.github.com/v3/activity/events/) via the GitHub API.

> Idea and text from [Nick Drewe](https://twitter.com/nickdrewe).

> Source: [https://thedatapack.com/tools/find-github-user-email/](https://thedatapack.com/tools/find-github-user-email/)

**Prerequisites**

- [Python 3](https://www.python.org/download/releases/3.0/)

**Installation**

```auto
git clone https://github.com/GONZOsint/gitrecon.gitcd gitrecon/python3 -m pip install -r requirements.txt

```

It is possible to use a [Github](https://github.com/settings/tokens)access token by editing line 23 of the gitrecon.py file

```auto
token = '<Access token here>'

```

**Usage**

```auto
usage: gitrecon.py [-h] [-a] [-o] usernamepositional arguments: usernameoptional arguments: -h, --help show this help message and exit -a, --avatar download avatar pic -o, --output save output as json

```

 ![image](https://onehack.st/uploads/default/original/3X/f/0/f0f2feb00c8d4c01bcd3a65a11c1891fe6440084.png)

**Features**

- **Profile info**

- **Extract Orgs**

- **Search for leaked emails on commits**

**Prevention**

To avoid this type of leaks, certain configurations can be made on Github:

Settings url: [https://github.com/settings/emails](https://github.com/settings/emails)

- Keep my email addresses private
- Block command line pushes that expose my email

## GitHub:

> **[GitHub - GONZOsint/gitrecon: OSINT tool to get information from a Github and...](https://github.com/GONZOsint/gitrecon)**
>
> OSINT tool to get information from a Github and Gitlab profile and find user's email addresses leaked on commits.