# Contributing to Awesome VPN Leak Detection

Thanks for considering a contribution.

## How to submit

1. Fork the repository.
2. Add your entry to the appropriate section in `README.md`, alphabetically when possible.
3. Open a pull request with the following template :

```
**Tool/resource name** :
**Category** :
**License (if applicable)** :
**Why it belongs here** :
**Last activity / publication date** :
```

## Inclusion criteria

- **Directly related** to detecting, measuring or remediating VPN leaks (DNS, WebRTC, IPv6, TCP timestamps, MTU fingerprinting, kill-switch failures, application-level leaks).
- **Reproducible** : a reader should be able to run the tool or read the paper without paywall.
- **Active or seminal** : actively maintained (last release < 2 years) OR academically significant.
- **No affiliate spam** : VPN provider websites are listed only when they ship substantive open-source tooling, methodology or research. Reviews/blog posts about specific providers belong elsewhere.

## What to avoid

- Marketing pages disguised as tools.
- Closed-source tools without a public technical writeup.
- Generic privacy tools that don't specifically address VPN leaks.

## Style

- Keep one line per entry.
- Use the existing table or bullet format of each section.
- Link directly to source code or published paper, not to landing pages.

## License of contributions

By contributing you agree that your additions are released under CC0 (public domain).
