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.
Website Team
Team members who focus specifically on eslint.org
Support Team
Folks who help in Discord and discussions.
-
Burak Yigit Kaya@BYK
Helping engineers help themselves help us all. Sr. SRE at @bloomberg, formerly @formsort, @getsentry, @facebook, @disqus, always a Mozillian
-
Samuel Roldan@sam3k
I am a staff frontend engineer with 19 years of experience architecting 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
-
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
-
Pig Fang@g-plane
-
Anix@anikethsaha
-
YeonJuan@yeonjuan