Add community health files

Author: Poryaei

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+## Summary
+
+- What does this change do?
+
+## Why
+
+- Why is this change needed?
+
+## Validation
+
+- [ ] `python -m pytest -q`
+- [ ] README or docs updated if behavior changed
+- [ ] New or updated tests added for the change
+
+## Notes
+
+- Any extra context, tradeoffs, or follow-up work?

CODE_OF_CONDUCT.md

@@ -0,0 +1,32 @@
+# Code of Conduct
+
+## Our Commitment
+
+We want `pine-script-validator` to be a respectful, constructive, and technically honest project for everyone.
+
+Contributors, users, and maintainers are expected to:
+
+- communicate respectfully
+- assume good intent while staying clear and direct
+- welcome questions from people with different experience levels
+- focus feedback on code, behavior, and ideas rather than people
+
+## Expected Behavior
+
+- be respectful in discussions, issues, and pull requests
+- provide actionable technical feedback
+- keep disagreements professional and specific
+- help maintain a collaborative environment
+
+## Unacceptable Behavior
+
+- harassment, insults, or personal attacks
+- discriminatory language or behavior
+- bad-faith arguments or repeated hostile interactions
+- publishing private information without permission
+
+## Enforcement
+
+If you experience or witness unacceptable behavior, open a private security-style report through the repository maintainers or, if needed, open an issue requesting moderator attention without sharing sensitive personal information.
+
+Project maintainers may remove, edit, or reject comments, issues, or pull requests that do not align with this Code of Conduct.

SECURITY.md

@@ -0,0 +1,22 @@
+# Security Policy
+
+## Supported Versions
+
+Security handling currently applies to the latest code on the `main` branch.
+
+## Reporting A Vulnerability
+
+If you discover a security issue, please do not open a public issue with exploit details.
+
+Instead:
+
+1. Open a GitHub issue only if the report can be made safely without exposing sensitive details.
+2. If the issue could expose users, environments, credentials, or unsafe behavior, contact the maintainer privately first.
+3. Include:
+   - a clear summary of the problem
+   - affected files or commands
+   - reproduction steps
+   - impact assessment
+   - any suggested mitigation
+
+We will review the report as quickly as possible and decide whether the issue should be handled privately before public disclosure.