Contributing and Support

Thank you for considering contributing to Levtus 🐧🐧🐧. Every issue, idea, example, and pull request helps.

Levtus is still in active development, so the API may change before the project reaches a stable v1.0. Keep that in mind while using or contributing to the project.

🐞 Reporting bugs

If you found a regular bug or quality-of-life issue, please open an issue on GitHub.

⚠️ Security vulnerabilities

If you believe you have found a security vulnerability, do not open a public issue.

Please use GitHub Security Advisories if available, or contact the maintainer privately by email with the subject line: “Security vulnerability found in Levtus”.

❓ Where to ask questions

If you have questions about the project, roadmap, API, or how to contribute, the best place is the GitHub Discussions page.

We welcome curiosity, feedback, and ideas.

💻 Contributing

There are many ways to help:

• report bugs and broken behavior
• suggest API improvements
• improve documentation
• write examples and sample apps
• submit pull requests for fixes or features

A small contribution is still a meaningful contribution.

🧭 Roadmap and versioning

Levtus is still in the v0.x phase, and the roadmap is intentionally evolving. The project is moving quickly, and breaking changes are still expected before the stable v1.0 release.

Current direction includes:

• routing and controller-style structure
• stronger middleware and filter capabilities
• better exception handling
• improved security and safe configuration
• better developer experience
• performance tuning and native/runtime improvements

This roadmap is a guiding vision, not a promise.

🐧 A quick reminder

Levtus is still early, but it is usable today. If you enjoy the project, we would really appreciate your support.

That includes giving Levtus a star 🌟🐧 and helping improve it with feedback, docs, or code.