A modern, secure web application for managing Discord webhooks with features for deleting and sending messages. Built with Express.js and Supabase authentication.
- 🔒 Secure Webhook Deletion: Safely remove unwanted Discord webhooks
- 📨 Message Sender: Send custom messages through webhooks (requires authentication)
- 🎨 Modern UI/UX: Clean, responsive design with dark/light theme support
- 🔐 Discord Authentication: Secure login using Discord OAuth
- 🌐 Cross-Platform: Works on all modern browsers
- Frontend: HTML5, CSS3, JavaScript
- Backend: Node.js, Express.js
- Authentication: Supabase Auth
- HTTP Client: Axios
- Additional: Chart.js (for future analytics)
- Node.js (v14 or higher)
- npm or yarn
- Discord application credentials
- Supabase account and project
- Clone the repository:
git clone /~https://github.com/ZerroDevs/WebhookDeleter.git
cd WebhookDeleter
- Install dependencies:
npm install
- Create a
.env
file in the root directory with the following variables:
SUPABASE_URL=your_supabase_url
SUPABASE_ANON_KEY=your_supabase_anon_key
- Start the server:
npm start
The application will be available at http://localhost:3000
- Navigate to the Webhook Deleter page
- Enter the webhook URL you want to delete
- Click "Delete Webhook"
- Confirm the deletion
- Log in with your Discord account
- Navigate to the Webhook Sender page
- Enter the webhook URL
- Customize your message with:
- Custom username
- Avatar URL
- Embed options
- Click "Send Message"
- All requests are validated server-side
- CORS protection enabled
- Authentication required for sensitive operations
- Secure headers implemented
- Environment variables for sensitive data
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature
) - Commit your changes (
git commit -m 'Add some amazing feature'
) - Push to the branch (
git push origin feature/amazing-feature
) - Open a Pull Request
This project is licensed under the MIT License - see the LICENSE file for details.
Created and maintained by ZeroNux
For support, please open an issue in the GitHub repository or contact the maintainers.