showExposedGitHubEmails
Is a crawler which lists all email addresses used in commits of a specific GitHub user using the GitHub API.
It iterates through all public respositories owned by the user and all commits in each of these repositories.
Installation
Install the package with pip
pip install exposed-github-user-emails-scanner
Usage
Type showExposedGitHubEmails --help to view the help.
usage: showExposedGitHubEmails [OPTION]... -u USERNAME
A crawler which lists all email addresses used in commits of a specific GitHub user using the GitHub API.
optional arguments:
-h, --help show this help message and exit
-u USER, --user USER username of the user whose public repositories should be scanned
-r REPOSITORY, --repository REPOSITORY
name of specific repository which should be scanned (default is all repositories)
-t TOKEN, --token TOKEN
provide a GitHub token to increase the API quota which can be used by this script
-v, --verbose verbose mode
-d DELAY, --delay DELAY
the delay between to requests in seconds (default is 1 second)
--api-url API_URL specify the URL to the GitHub Api (default is "https://api.github.com")
--no-forks ignore forked repositories
Example
$ showExposedGitHubEmails -u AFictionalUsername
[+] Scan for public repositories of user AFictionalUsername
[+] Found 4 public repositories
[+] Scan repository my_first_project
[+] Scan repository project_2
[+] Exposed emails and names:
41277220+aficionalusername@users.noreply.github.com - John Doe
john.doe@hotmail.com - JD; John Doe
john.doe@company.com - John Doe (Software Eng.)
Metadata
Release files for exposed-github-user-emails-scanner 1.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| exposed_github_user_emails_scanner-1.0.7.tar.gz | 5.1 kB | Without provenance | Details for exposed_github_user_emails_scanner-1.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| exposed_github_user_emails_scanner-1.0.7-py3-none-any.whl | Python 3 | none | any | Details for exposed_github_user_emails_scanner-1.0.7-py3-none-any.whl |
Total release size: 11.3 kB
Release files / exposed_github_user_emails_scanner-1.0.7.tar.gz
| Download URL | exposed_github_user_emails_scanner-1.0.7.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da66aebf27b303a2ead9ca6054470f591943a329179d26f1c56745204d7b33a8
|
|
BLAKE2b-256 checksum How to use checksums |
b57a0c3c1ae8a27bea1af72553f91c35b97ddbafef120bd25eb90b4eb5d53f0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Release files / exposed_github_user_emails_scanner-1.0.7-py3-none-any.whl
| Download URL | exposed_github_user_emails_scanner-1.0.7-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
877d27f8eb6e15826fda2ba19d54487206ebca6b2f9a0360330b7d9c3b4001a8
|
|
BLAKE2b-256 checksum How to use checksums |
644c84ac0b7d7951a154f06c6dfc9b3118599ab35b31337cbd318871af324c91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Security for exposed-github-user-emails-scanner 1.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.