burner-bouncer solves a common but overlooked problem — disposable email detection — with zero runtime dependencies, no API calls, and a bundled blocklist of 629 real domains. Ships as both an npm package (TypeScript, ESM + CJS) and a Python package with an identical API.
Which criterion does it meet? (pick one)
Industry Standard - The go-to tool for a specific use case
Rising Star - 5000+ stars in < 2 years, significant adoption
Most email validation libraries focus on format checking. burner-bouncer specifically targets disposable/burner domains and is the only library to ship the same API in both JavaScript and Python backed by a single shared community-maintained blocklist.
If similar entries exist, what makes this one unique?
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/vinta/awesome-python/pull/3109
**Author:** [@grocerysushi](https://github.com/grocerysushi)
**Created:** 5/5/2026
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `patch-1`
---
### 📝 Commits (1)
- [`2e90f6e`](https://github.com/vinta/awesome-python/commit/2e90f6ee208865fcc773cf9fd25a249ee25ca3ed) Add burner-bouncer to email libraries section
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
Added burner-bouncer to the list of email libraries.
## Project
[burner-bouncer](https://github.com/grocerysushi/burner-bouncer)
## Checklist
- [x] One project per PR
- [x] PR title format: `Add burner-bouncer`
- [x] Entry format: [burner-bouncer](https://github.com/grocerysushi/burner-bouncer) - Zero-dependency disposable email detector.
- [x] Description is concise and short
## Why This Project Is Awesome
burner-bouncer solves a common but overlooked problem — disposable email detection — with zero runtime dependencies, no API calls, and a bundled blocklist of 629 real domains. Ships as both an npm package (TypeScript, ESM + CJS) and a Python package with an identical API.
Which criterion does it meet? (pick one)
- [ ] **Industry Standard** - The go-to tool for a specific use case
- [ ] **Rising Star** - 5000+ stars in < 2 years, significant adoption
- [x] **Hidden Gem** - Exceptional quality, solves niche problems elegantly
Explain:
## How It Differs
Most email validation libraries focus on format checking. burner-bouncer specifically targets disposable/burner domains and is the only library to ship the same API in both JavaScript and Python backed by a single shared community-maintained blocklist.
If similar entries exist, what makes this one unique?
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/vinta/awesome-python/pull/3109
Author: @grocerysushi
Created: 5/5/2026
Status: ❌ Closed
Base:
master← Head:patch-1📝 Commits (1)
2e90f6eAdd burner-bouncer to email libraries section📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
Added burner-bouncer to the list of email libraries.
Project
burner-bouncer
Checklist
Add burner-bouncerWhy This Project Is Awesome
burner-bouncer solves a common but overlooked problem — disposable email detection — with zero runtime dependencies, no API calls, and a bundled blocklist of 629 real domains. Ships as both an npm package (TypeScript, ESM + CJS) and a Python package with an identical API.
Which criterion does it meet? (pick one)
Explain:
How It Differs
Most email validation libraries focus on format checking. burner-bouncer specifically targets disposable/burner domains and is the only library to ship the same API in both JavaScript and Python backed by a single shared community-maintained blocklist.
If similar entries exist, what makes this one unique?
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.