Community profile improvements (PR template, CoC, Security)

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,61 @@
+## Description
+
+Please provide a clear description of the changes included in this pull request.
+
+Explain:
+
+* What problem this PR solves
+* Why the change is necessary / wanted
+* Any relevant context or background
+
+---
+
+## Type of Change
+
+Please check the relevant option:
+
+* [ ] Bug fix
+* [ ] New feature
+* [ ] Performance improvement
+* [ ] Refactoring
+* [ ] Documentation update
+* [ ] Build / CI change
+* [ ] Other (please describe)
+
+---
+
+## Related Issues
+
+Link any related issues or pull requests here.
+
+Example:
+Fixes #123
+Related to #456
+
+---
+
+## Testing
+
+Before submitting, please test you changes accordingly. Check the list bellow:
+
+* Tested on a clean SphereServer instance with latest ScriptPack
+* No regressions in existing functionality
+* Added or updated tests (if applicable)
+
+---
+
+## Checklist
+
+Please confirm the following before submitting:
+
+* [ ] Code compiles successfully
+* [ ] Changes follow the project's coding style
+* [ ] No unrelated code was modified
+* [ ] Documentation updated where necessary
+* [ ] This PR does not introduce breaking changes (or they are documented)
+
+---
+
+## Additional Notes
+
+Add any other information reviewers should know.

CODE_OF_CONDUCT.md

@@ -0,0 +1,91 @@
+# Code of Conduct
+
+## Pledge
+
+We as contributors and maintainers pledge to make participation in the SphereServer project and its community a harassment-free experience for everyone.
+
+We are committed to creating an open, welcoming, and inclusive environment for all participants, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+---
+
+## Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Giving and accepting constructive feedback gracefully
+* Focusing on what is best for the project and community
+* Showing empathy and patience with other contributors
+* Helping new contributors understand the project
+
+Examples of unacceptable behavior include:
+
+* Harassment, trolling, or insulting comments
+* Personal attacks or derogatory remarks
+* Discriminatory or hateful language
+* Publishing others’ private information without explicit permission
+* Intentionally disruptive behavior in issues, pull requests, or discussions
+* Repeated spam or off-topic posts
+
+---
+
+## Contribution Etiquette
+
+To keep collaboration productive:
+
+* Keep issue reports clear and reproducible.
+* Avoid opening duplicate issues.
+* Use respectful and professional language in discussions.
+* Technical disagreements should focus on code and design decisions, not individuals.
+* Major changes should be discussed in an issue before submitting a pull request.
+
+---
+
+## Maintainer Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing the standards of acceptable behavior.
+
+Maintainers may:
+
+* Remove or edit comments, commits, issues, or pull requests that violate this Code of Conduct
+* Temporarily or permanently ban contributors who engage in inappropriate behavior
+* Moderate discussions to maintain a respectful environment
+
+All moderation actions should be applied fairly and consistently.
+
+---
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project maintainers.
+
+All reports will be reviewed and investigated fairly and confidentially.
+
+Possible enforcement actions include:
+
+* Warning
+* Temporary restriction from discussions
+* Locking or removing issue threads
+* Blocking a user from the repository
+* Permanent ban from contributing
+
+---
+
+## Scope
+
+This Code of Conduct applies to all project spaces, including:
+
+* GitHub issues
+* Pull requests
+* Discussions
+* Documentation contributions
+* Any official project communication channels
+
+It also applies when a contributor is representing the project in public spaces.
+
+---
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), a widely used open-source community standard.

SECURITY.md

@@ -0,0 +1,64 @@
+# Security Policy
+
+## Supported Versions
+
+Security fixes are typically applied to the latest maintained version of SphereServer, which is currently **Nightly 
+build** from master branch.
+
+If you are running an older version, please upgrade before reporting issues.
+
+---
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability in SphereServer, please report it responsibly.
+
+Do **not** create a public GitHub issue for security vulnerabilities.
+
+Instead:
+
+1. Contact the maintainers privately.
+2. Provide a detailed description of the vulnerability.
+3. Include reproduction steps if possible.
+
+Your report should include:
+
+* Description of the vulnerability
+* Steps to reproduce
+* Potential impact
+* Affected versions
+* Suggested fix (if available)
+
+---
+
+## Responsible Disclosure
+
+We ask security researchers to follow responsible disclosure practices:
+
+* Allow maintainers reasonable time to investigate and fix the issue
+* Do not publicly disclose the vulnerability before a fix is available
+* Avoid exploiting the vulnerability beyond proof-of-concept
+
+---
+
+## Security Updates
+
+Security patches will be released as soon as reasonably possible after confirmation of the issue.
+
+When a vulnerability is fixed:
+
+* A patch will be committed
+* Release notes may mention the fix
+* Credit may be given to the reporter (if desired)
+
+---
+
+## Scope
+
+This policy applies to the SphereServer codebase, including:
+
+* Core server code
+* Network handling
+* Script engine
+* Authentication and account management
+* Build system and dependencies