···11-# These are supported funding model platforms
22-33-github: [IntegerAlex]
44-patreon: # Replace with a single Patreon username
55-open_collective: # Replace with a single Open Collective username
66-ko_fi: # Replace with a single Ko-fi username
77-tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
88-community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
99-liberapay: # Replace with a single Liberapay username
1010-issuehunt: # Replace with a single IssueHunt username
1111-otechie: # Replace with a single Otechie username
1212-lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
1313-polar: # Replace with a single Polar username
1414-custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']
-20
.github/ISSUE_TEMPLATE/feature_request.md
···11----
22-name: Feature request
33-about: Suggest an idea for this project
44-title: ''
55-labels: ''
66-assignees: ''
77-88----
99-1010-**Is your feature request related to a problem? Please describe.**
1111-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
1212-1313-**Describe the solution you'd like**
1414-A clear and concise description of what you want to happen.
1515-1616-**Describe alternatives you've considered**
1717-A clear and concise description of any alternative solutions or features you've considered.
1818-1919-**Additional context**
2020-Add any other context or screenshots about the feature request here.
···11-# Contributor Covenant Code of Conduct
22-33-## Our Pledge
44-55-We as members, contributors, and leaders pledge to make participation in our
66-community a harassment-free experience for everyone, regardless of age, body
77-size, visible or invisible disability, ethnicity, sex characteristics, gender
88-identity and expression, level of experience, education, socio-economic status,
99-nationality, personal appearance, race, religion, or sexual identity
1010-and orientation.
1111-1212-We pledge to act and interact in ways that contribute to an open, welcoming,
1313-diverse, inclusive, and healthy community.
1414-1515-## Our Standards
1616-1717-Examples of behavior that contributes to a positive environment for our
1818-community include:
1919-2020-* Demonstrating empathy and kindness toward other people
2121-* Being respectful of differing opinions, viewpoints, and experiences
2222-* Giving and gracefully accepting constructive feedback
2323-* Accepting responsibility and apologizing to those affected by our mistakes,
2424- and learning from the experience
2525-* Focusing on what is best not just for us as individuals, but for the
2626- overall community
2727-2828-Examples of unacceptable behavior include:
2929-3030-* The use of sexualized language or imagery, and sexual attention or
3131- advances of any kind
3232-* Trolling, insulting or derogatory comments, and personal or political attacks
3333-* Public or private harassment
3434-* Publishing others' private information, such as a physical or email
3535- address, without their explicit permission
3636-* Other conduct which could reasonably be considered inappropriate in a
3737- professional setting
3838-3939-## Enforcement Responsibilities
4040-4141-Community leaders are responsible for clarifying and enforcing our standards of
4242-acceptable behavior and will take appropriate and fair corrective action in
4343-response to any behavior that they deem inappropriate, threatening, offensive,
4444-or harmful.
4545-4646-Community leaders have the right and responsibility to remove, edit, or reject
4747-comments, commits, code, wiki edits, issues, and other contributions that are
4848-not aligned to this Code of Conduct, and will communicate reasons for moderation
4949-decisions when appropriate.
5050-5151-## Scope
5252-5353-This Code of Conduct applies within all community spaces, and also applies when
5454-an individual is officially representing the community in public spaces.
5555-Examples of representing our community include using an official e-mail address,
5656-posting via an official social media account, or acting as an appointed
5757-representative at an online or offline event.
5858-5959-## Enforcement
6060-6161-Instances of abusive, harassing, or otherwise unacceptable behavior may be
6262-reported to the community leaders responsible for enforcement at
6363-https://www.linkedin.com/in/akshat-kotpalliwar-554944258/.
6464-All complaints will be reviewed and investigated promptly and fairly.
6565-6666-All community leaders are obligated to respect the privacy and security of the
6767-reporter of any incident.
6868-6969-## Enforcement Guidelines
7070-7171-Community leaders will follow these Community Impact Guidelines in determining
7272-the consequences for any action they deem in violation of this Code of Conduct:
7373-7474-### 1. Correction
7575-7676-**Community Impact**: Use of inappropriate language or other behavior deemed
7777-unprofessional or unwelcome in the community.
7878-7979-**Consequence**: A private, written warning from community leaders, providing
8080-clarity around the nature of the violation and an explanation of why the
8181-behavior was inappropriate. A public apology may be requested.
8282-8383-### 2. Warning
8484-8585-**Community Impact**: A violation through a single incident or series
8686-of actions.
8787-8888-**Consequence**: A warning with consequences for continued behavior. No
8989-interaction with the people involved, including unsolicited interaction with
9090-those enforcing the Code of Conduct, for a specified period of time. This
9191-includes avoiding interactions in community spaces as well as external channels
9292-like social media. Violating these terms may lead to a temporary or
9393-permanent ban.
9494-9595-### 3. Temporary Ban
9696-9797-**Community Impact**: A serious violation of community standards, including
9898-sustained inappropriate behavior.
9999-100100-**Consequence**: A temporary ban from any sort of interaction or public
101101-communication with the community for a specified period of time. No public or
102102-private interaction with the people involved, including unsolicited interaction
103103-with those enforcing the Code of Conduct, is allowed during this period.
104104-Violating these terms may lead to a permanent ban.
105105-106106-### 4. Permanent Ban
107107-108108-**Community Impact**: Demonstrating a pattern of violation of community
109109-standards, including sustained inappropriate behavior, harassment of an
110110-individual, or aggression toward or disparagement of classes of individuals.
111111-112112-**Consequence**: A permanent ban from any sort of public interaction within
113113-the community.
114114-115115-## Attribution
116116-117117-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118118-version 2.0, available at
119119-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120120-121121-Community Impact Guidelines were inspired by [Mozilla's code of conduct
122122-enforcement ladder](https://github.com/mozilla/diversity).
123123-124124-[homepage]: https://www.contributor-covenant.org
125125-126126-For answers to common questions about this code of conduct, see the FAQ at
127127-https://www.contributor-covenant.org/faq. Translations are available at
128128-https://www.contributor-covenant.org/translations.
-7
CONTRIBUTING.md
···11-# Contributing to Disposable Email Detector
22-33-We welcome and appreciate your contributions! Here's how you can get involved:
44-55-* **Updating Disposable Domains:** Help keep the `index.json` up-to-date.
66-* **Reporting Issues:** If you find a bug, please open an issue with a clear description.
77-* **Code Improvements:** Feel free to suggest code enhancements or refactorings by submitting a pull request.
-44
LEARN.md
···11-# Learning Disposable Email Detector
22-33-Welcome to the Disposable Email Detector project! This guide is designed to help you understand, use, and contribute to the project effectively.
44-55-## Introduction
66-77-Disposable Email Detector is a Node.js utility designed to identify disposable email addresses and enhance email validation processes. This guide will walk you through essential aspects of using and contributing to the project.
88-99-## Getting Started
1010-1111-### Installation
1212-1313-To use Disposable Email Detector, you need to install it in your Node.js project. Run the following command:
1414-1515-```bash
1616-npm install disposable-email-detector
1717-1818-import disposableEmailDetector from 'disposable-email-detector';
1919-2020-const email = 'test@mailinator.com';
2121-2222-disposableEmailDetector(email)
2323- .then((response) => console.log(response));
2424-```
2525-Contributing
2626-We welcome contributions from the community! Whether you want to report a bug, suggest an enhancement, or contribute code, your input is valuable.
2727-2828-Reporting Issues
2929-If you encounter issues or have suggestions, please open an issue on our GitHub repository.
3030-3131-Development Setup
3232-To set up the project for development:
3333-3434-- Clone the repository.
3535-- Install dependencies: npm install
3636-- Make your changes and test.
3737-- Pull Requests
3838-- Submit a pull request with your changes, and we'll review it as soon as possible.
3939-4040-Security
4141-If you discover security vulnerabilities, please follow our Security Policy to report them responsibly.
4242-4343-4444-
+1-1
LICENSE
LICENSE.md
···11MIT License
2233-Copyright (c) 2024 Akshat Kotpalliwar
33+Copyright (c) 2025 Jasper Mayone (modifed from Akshat Kotpalliwar)
4455Permission is hereby granted, free of charge, to any person obtaining a copy
66of this software and associated documentation files (the "Software"), to deal
+13-17
README.md
···11-# Disposable Email Detector
11+# @jaspermayone/disposable-email-detector
2233-[](https://deepscan.io/dashboard#view=project&tid=23370&pid=26631&bid=850159)
44-
55-[](https://app.deepsource.com/gh/IntegerAlex/disposable-email-detector/)
33+> [!IMPORTANT]
44+> This is a fork of [IntegerAlex/disposable-email-detectork](https://github.com/IntegerAlex/disposable-email-detectork), with some improvements and bugfixes. Our base version 1.0.0. was based from Alex's version 3.0.0, specifically commit [da406b2](https://github.com/IntegerAlex/disposable-email-detector/commit/da406b2cbcf0478ab49faabda618be1b588763dc)
6577-
88-
66+
77+
98109## Overview
11101212-The `disposable-email-detector` is a TypeScript utility designed to identify disposable email addresses, providing developers with a tool to enhance email verification processes.
1313-1414-## Demo
1515-1616-DEMO : [LIVE](https://disposable-email-detector-demo.vercel.app/)
1717-DEMO REPO : [REPO](https://github.com/IntegerAlex/disposable-email-detector-demo)
1111+`@jaspermayone/disposable-email-detector` is a TypeScript utility designed to identify disposable email addresses, providing developers with a tool to enhance email verification processes.
18121913## Features
2014···3226### Implementation Details
33273428```javascript
3535- npm i disposable-email-detector
2929+ npm i @jaspermayone/disposable-email-detector
3630```
37313832```javascript
3939- import disposableEmailDetector from 'disposable-email-detector';
3333+import disposableEmailDetector from "@jaspermayone/disposable-email-detector";
40344141- const email = 'test@mailinator.com';
3535+const email = "test@example.com";
42364343- disposableEmailDetector(email)
4444- .then((response) => console.log(response)); // true
3737+disposableEmailDetector(email).then((response) => console.log(response)); // true
4538```
46394740The disposableEmailDetector function reads a list of disposable email domains from index.json. It checks whether the provided email address belongs to a disposable domain and returns a boolean indicating the result.
···5952## License
60536154This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
5555+5656+```
5757+6258```
-32
SECURITY.md
···11-# Security Policy
22-33-## Supported Versions
44-55-Use this section to inform users about which versions of your project are currently being supported with security updates.
66-77-| Version | Supported |
88-| ------- | ------------------ |
99-| 1.0.2 | :white_check_mark: |
1010-| 1.0.x | :x: |
1111-1212-## Reporting a Vulnerability
1313-1414-If you discover a security vulnerability within the supported version (1.0.2), please follow these steps:
1515-1616-1. **Publicly Disclosed Vulnerabilities:**
1717- - If you discover a security vulnerability that could be exploited by others, please do not disclose it publicly. Instead, report it directly to our security team.
1818-1919-2. **Reporting Process:**
2020- - Send an email to security@example.com with a detailed description of the vulnerability.
2121- - Include steps to reproduce the vulnerability, potential impact, and any other relevant information.
2222-2323-3. **Response Time:**
2424- - Our security team will acknowledge your report within 48 hours.
2525-2626-4. **Security Updates:**
2727- - If the vulnerability is accepted, we will work on releasing a security update promptly.
2828-2929-5. **Disclosure Policy:**
3030- - We follow a coordinated disclosure policy, and we appreciate your responsible disclosure of security issues.
3131-3232-Thank you for helping to keep our project secure!