Add CONTRIBUTING.md and SECURITY.md files with guidelines for contributions and vulnerability reporting

Author: rcalicdan

CONTRIBUTING.md

@@ -0,0 +1,26 @@
+# Contributing to TypePHP
+
+Thank you for showing interest in contributing to this TypePHP library! Contributions are essential for building a robust type-safe ecosystem for the PHP community.
+
+This library is designed to be a reliable foundation for high-performance applications. To achieve this, it maintains rigorous standards for code quality and developer experience.
+
+## Development Workflow
+
+To ensure consistency across the ecosystem, this repository requires the following workflow:
+
+1. **Fork and Branch**: Fork the repository and create a feature branch from `main`.
+2. **Dependencies**: Install development tools using `composer install`.
+3. **Coding Standards**: This project follows strict PSR-12 standards. Use Laravel Pint to format code: `./vendor/bin/pint`.
+4. **Static Analysis**: Code must be predictable and type-safe. It must pass PHPStan at the maximum level: `./vendor/bin/phpstan analyse`.
+5. **Testing**: This project uses Pest. Ensure the test suite passes completely: `./vendor/bin/pest`.
+6. **Strict Typing**: Every PHP file must begin with `declare(strict_types=1);`.
+
+
+## Pull Request Process
+
+1. **Start with an Issue**: Before writing code, please open an issue to discuss the bug or the proposed feature.
+2. **Tests are Required**: Every Pull Request must include automated tests that cover the new logic or prevent the bug from recurring.
+
+---
+
+The Hibla ecosystem thanks you for your time and effort!

LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Reymart Calicdan <reymart.calicdan06@gmail.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

Security.md

@@ -0,0 +1,29 @@
+# Security Policy
+
+This Hibla library takes the security of its users and their data seriously. 
+
+## Supported Versions
+
+During the Alpha and Beta development phases, security updates are provided for the latest release only.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 1.0.x   | :white_check_mark: |
+| < 1.0   | :x:                |
+
+## Reporting a Vulnerability
+
+If a security vulnerability is discovered within this library, please report it privately to ensure the safety of all users.
+
+Reports should be sent via e-mail to **Reymart A. Calicdan** at **reymart.calicdan06@gmail.com**.
+
+**Please do not use public GitHub issues to report security vulnerabilities.**
+
+### The Response Process
+
+1. **Acknowledgment**: A response acknowledging the report will be sent within 48 hours.
+2. **Investigation**: The vulnerability will be investigated and confirmed in a private environment.
+3. **Resolution**: Once a fix is developed, it will be review and tested before being tagged in a new release.
+4. **Disclosure**: After the fix is public, credit will be given to the reporter for their contribution to the security of the Hibla ecosystem (unless anonymity is requested).
+
+Thank you for helping keep Hibla secure for everyone.