A Val Town project that finds email addresses associated with a GitHub user by analyzing their public commit history using multiple methods.

Visit the live demo to try it out!

• Dual Method Approach: Uses two different GitHub API strategies to maximize email discovery
• Smart Early Stopping: Stops after the first method if emails are found, saving API calls
• Smart Filtering: Automatically filters out GitHub's noreply email addresses
• Ranked Results: Shows emails ranked by frequency of use in commits
• Rate Limit Friendly: Includes delays and error handling to respect GitHub's API limits
• Clean UI: Modern, responsive interface built with Hono JSX and Tailwind CSS
• Modular Architecture: Well-organized codebase with separated concerns

The tool uses two complementary methods to find email addresses:

• Fetches the user's recent public events (up to 100)
• Filters for PushEvent activities
• Extracts email addresses from commit authors in those events
• Pros: Fast, single API call
• Cons: Limited to recent public activity, may miss older emails

• Gets the user's 10 most recently updated repositories
• Fetches the last 10 commits from each repository (authored by the user)
• Extracts email addresses from commit metadata
• Pros: More comprehensive, can find emails from older commits
• Cons: Multiple API calls, slower execution

• Runs both methods simultaneously using Promise.allSettled
• Merges and deduplicates results
• Aggregates commit counts across both methods
• Provides fallback if one method fails

├── github-events.ts    # Core email extraction logic
├── demo.tsx           # Web interface (HTTP endpoint)
└── README.md          # This file

• Runtime: Deno on Val Town
• Framework: Hono for HTTP handling
• UI: Server-side JSX with Tailwind CSS
• API: GitHub REST API v4

• Uses Val Town's proxied fetch to help with rate limits
• Supports optional GITHUB_TOKEN environment variable for higher rate limits
• Includes 100ms delays between repository API calls
• Graceful error handling for failed requests

GITHUB_TOKEN=your_github_personal_access_token

Adding a GitHub token increases your rate limit from 60 to 5,000 requests per hour.

1. Clone or fork this Val Town project
2. Set up your GITHUB_TOKEN if desired
3. The main entry point is demo.tsx (HTTP endpoint)

import { 
  getGithubUserEmail,           // Combined approach (recommended)
  getGithubUserEmailFromEvents, // Events-only method
  getGithubUserEmailFromCommits // Commits-only method
} from "./github-events.ts";

// Get emails using both methods
const emails = await getGithubUserEmail("username");

// Results format
interface EmailOccurrence {
  username: string;    // Author name from commits
  email: string;       // Email address
  commitCount: number; // Number of commits using this email
}

# Web interface
GET /?username=octocat

# Returns HTML page with results

• Only analyzes public repositories and commits
• Respects users who have configured private emails
• Filters out GitHub's @users.noreply.github.com addresses
• Use responsibly and respect privacy

• GitHub API rate limits (60/hour without token, 5000/hour with token)
• Only finds emails from commits where the user is the author
• May miss emails from private repositories or private commits
• Results depend on user's commit history and email configuration

• Email addresses found may be outdated
• Users can configure different emails for different repositories
• Some commits may use organization or work emails
• Results are ranked by frequency, not recency

The application handles various error scenarios:

• Invalid usernames
• API rate limit exceeded
• Network timeouts
• Private or empty repositories
• Malformed API responses

Errors are logged to console and displayed to users with helpful messages.

This is a Val Town project. To contribute:

1. Fork the project in Val Town
2. Make your changes
3. Test thoroughly
4. Share your improvements!

This project is open source and available under standard Val Town terms.

This tool is for educational and legitimate research purposes only. Always respect privacy, follow GitHub's Terms of Service, and use responsibly. The authors are not responsible for misuse of this tool.