Update CODE_OF_CONDUCT.md, add CONTRIBUTING.md, and enhance SECURITY.md

- Updated the contact email in CODE_OF_CONDUCT.md for reporting unacceptable behavior.
- Added a comprehensive CONTRIBUTING.md file detailing setup, testing, and contribution guidelines.
- Expanded SECURITY.md to include a section on reporting vulnerabilities and best practices for using the SDK securely.

Author: franciscbalint

CMakeLists.txt

@@ -1,5 +1,5 @@
 cmake_minimum_required(VERSION 3.20)
-project(ZeroBounce VERSION 1.0.0 LANGUAGES CXX)
+project(ZeroBounce VERSION 1.1.1 LANGUAGES CXX)
 
 set(CMAKE_CXX_STANDARD 20)
 set(CMAKE_CXX_STANDARD_REQUIRED ON)

CODE_OF_CONDUCT.md

@@ -0,0 +1,48 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and maintainers of the Zero Bounce C++ API Wrapper pledge to make participation in our project and community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy toward other community members
+
+Examples of unacceptable behavior:
+
+* The use of sexualized language or imagery, and unwelcome sexual attention or advances
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information (e.g. physical or email address) without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and also applies when an individual is representing the project or its community in public spaces. Examples of representing the project include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project team at **integrations@zerobounce.net**. All complaints will be reviewed and investigated promptly and fairly. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][version].
+
+[homepage]: https://www.contributor-covenant.org
+[version]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

CONTRIBUTING.md

@@ -0,0 +1,54 @@
+# Contributing to Zero Bounce C++ API Wrapper
+
+Thank you for your interest in contributing. This document explains how to get set up and submit changes.
+
+## Code of Conduct
+
+By participating in this project, you agree to uphold our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Getting Started
+
+See the [README](README.md) for prerequisites, setup, and how to run tests.
+
+## How to Contribute
+
+### Reporting Bugs
+
+Open an [issue](https://github.com/zerobounce/zerobounce-cpp-api-wrapper/issues) and include:
+
+* Environment details (compiler, OS)
+* Steps to reproduce
+* Expected vs actual behavior
+* Relevant code or error messages
+
+### Suggesting Changes
+
+* Check existing issues and pull requests first.
+* Open an issue to discuss larger changes or API design before coding.
+
+### Submitting Changes
+
+1. **Fork** the repository and create a branch from `main`:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+2. **Make your changes** and add or update tests where relevant.
+
+3. **Run the test suite** (see README) before submitting.
+
+4. **Commit** with a clear message (e.g. `Add X`, `Fix Y`).
+
+5. **Push** your branch and open a **Pull Request** against `main`.
+
+6. In the PR description, briefly explain what changed and why. Link any related issues.
+
+Maintainers will review and may request changes. Once approved, your PR can be merged.
+
+## Questions
+
+* [Zero Bounce API docs](https://www.zerobounce.net/docs/)
+* [Project homepage](https://zerobounce.net)
+* Contact: **integrations@zerobounce.net**
+
+Thanks for contributing.

SECURITY.md

@@ -1 +1,21 @@
 # Security Policy
+
+## Reporting a Vulnerability
+
+If you think you've found a security issue, please report it privately instead of opening a public issue.
+
+**Email:** integrations@zerobounce.net (use a subject like `[zerobounce-cpp-api-wrapper] Security`).
+
+We'll look into reports as we can. If the issue is in the Zero Bounce API or service rather than this wrapper, we may forward it to the right team.
+
+## Supported Versions
+
+We focus on the current release line for fixes. Using the latest release is recommended.
+
+## Tips for Using This Wrapper
+
+* Don't commit API keys or `.env` files—use environment variables or a secrets manager.
+* Keep dependencies up to date and upgrade when new versions are released.
+* The client uses HTTPS by default; avoid overriding to non-HTTPS in production.
+
+Thanks for helping keep things secure.