This file lists the people who maintain KubeArmor. The roles, requirements, and process for joining or leaving each tier are defined in GOVERNANCE.md.
Affiliations are disclosed per the vendor-neutrality clause in GOVERNANCE.md. If your affiliation changes, please open a pull request to this file within 30 days.
General contact: support@kubearmor.io reaches the Maintainer group. Use it for governance, code-of-conduct, or other project-level inquiries that should reach all Maintainers at once. For security reports, follow SECURITY.md. For real-time chat, see the Community page.
Maintainers have merge authority and share responsibility for the project's direction, releases, code of conduct, and security response.
The list is sorted alphabetically.
| Name | GitHub | Company |
|---|---|---|
| Achref Ben Saad | @achrefbensaad | AccuKnox |
| Ankur Kothiwal | @Ankurk99 | CERN |
| Anurag Kumar | @kranurag7 | Independent |
| Aryan Bakliwal | @AryanBakliwal | AccuKnox |
| Aryan Sharma | @Aryan-sharma11 | AccuKnox |
| Barun Acharya | @daemon1024 | Odigos |
| Jaehyun Nam | @nam-jaehyun | Dankook University |
| Rahul Jadhav | @nyrahul | AccuKnox |
| Ramakant Sharma | @rksharma95 | StepSecurity |
| Rishabh Soni | @rootxrishabh | RapidFort |
| Rudraksh Pareek | @DelusionalOptimist | CERN |
Reviewers have area-specific review authority on the parts of the codebase listed for them in CODEOWNERS. Their LGTM is a precondition for merging in their area, but they do not have merge authority themselves.
None yet recorded under the formalised Reviewer tier. See CODEOWNERS for current default reviewers; their status under the new governance is being reconciled.
Emeritus Maintainers have stepped down or have been moved to emeritus status under the inactivity rule in GOVERNANCE.md. They retain credit and may be re-invited if they become active again.
None yet recorded.
See the Roles section in GOVERNANCE.md for requirements, nomination, and voting process.
Open a pull request. Changes to the Maintainers list pass with a simple majority vote of the current Maintainers (1-week window), per GOVERNANCE.md. Changes to affiliations and contact details are merged by lazy consensus.