Meet our Team
These are the people who build and maintain ESLint.
Technical Steering Committee
The people who manage releases, review feature requests, and meet regularly to ensure ESLint is properly maintained.
-
Nicholas C. Zakas@nzakas
Creator of ESLint, independent software developer, consultant, coach, and author.
-
-
Reviewers
The people who review and implement new features.
Committers
The people who review and fix bugs and help triage issues.
-
Josh Goldberg ✨@JoshuaKGoldberg
Full time open source 💖✨ @typescript-eslint maintainer; @LearningTypeScript author; Microsoft MVP 🌟
-
Website Team
Team members who focus specifically on eslint.org
Support Team
Folks who help in Discord and discussions.
-
Samuel Roldan@sam3k
I am a frontend lead engineer with over two decades of experience architecting frontend web applications.
-
Kevin Partington@platinumazure
@eslint support team member. My open source participation will be limited as I continue to heal my depression and anxiety.
-
Alumni
Former team members who previously helped maintain ESLint.
-
Brett Zamir@brettz9
-
alberto@alberto
-
Burak Yigit Kaya@BYK
-
Mathias Schreck@lo1tuma
-
Michael Ficarra@michaelficarra
-
Jamund Ferguson@xjamundx
-
Mike Sherov@mikesherov
-
Henry@hzoo
-
Vitor Balocco@vitorbal
-
Bryan Mishkin@bmish
-
James Henry@JamesHenry
-
Oleg Gaidarenko@markelog
-
Michael Robinson@faceleg
-
Ilya Volodin@ilyavolodin
-
Brandon Mills@btmills
-
Toru Nagashima@mysticatea
-
Reyad Attiyat@soda0289
-
Sara Soueidan@SaraSoueidan
-
Victor Hom@VictorHom
-
Ian VanSchooten@IanVS
-
Gyandeep Singh@gyandeeps
-
Kai Cataldo@kaicataldo
-
Teddy Katz@not-an-aardvark
-
Mark Pedrotti@pedrottimark
-
Yosuke Ota@ota-meshi
-
Pig Fang@g-plane
-
Anix@anikethsaha
-
YeonJuan@yeonjuan
