ESLint relies on donations for ongoing maintenance and development. There are currently 174 companies, organizations, and individuals donating $10,130.00 each month to help us out.

Ways to donate

We accept donations through the following sites.

Open Collective

Open Collective

Our most popular plan for companies.

  • Donate directly to a 501(c)(6) non-profit
  • One-time and recurring donations
  • Pay by credit card, bank transfer, or PayPal
  • Set up an open source fund to donate to multiple projects
  • Available in most countries

GitHub Sponsors

Advanced features and reporting.

  • Donate through GitHub billing
  • One-time and recurring donations
  • Pay by credit card or use your existing billing relationship with GitHub (including invoicing)
  • Show a “sponsor” badge on your GitHub profile
  • Use your existing GitHub login

How the money is used

The ESLint project uses donated money to benefit the project and the ESLint community as a whole. In general, we spend money on these areas each month.

Team Development

We pay our team members an hourly rate based on their seniority, currently $80.00 USD/hour for TSC members and Reviewers and $50.00 USD/hour for committers.

Contributor Pool

We set aside $1,000.00 USD each month to pay outside contributors who have made significant contributions to the project. Contributions include submitting code, writing documentation, answering questions in our Discord server, and more. This money is allocated each month by the TSC.


We set aside $1,500.00 USD each month to help support our dependencies. We believe that open source projects who are lucky enough to get funded have a responsibility to help support the smaller projects they rely on.

Community Projects

We set aside $1,500.00 USD each month to help support plugins, parsers, and other projects that are of benefit to the ESLint ecosystem as a whole. We believe the strength of the project is in its ecosystem and we want to ensure important projects remain well-maintained.

Support Systems

We use a small amount each month to pay for software the team uses to help manage the project, which includes things like Google Workspace and cloud storage.

Graph visually representing approximate percentages of how the money is used and distributed between Team Development, Contributor Pool, Dependencies, Community Projects, and support systems.

Additionally, from time to time we use the funds to pay contractors to work on things that are important to the project and where the team doesn’t have the time or expertise to complete the work on their own. For example, we recently hired a designer and developer to redesign this website. We ensure that we spend less than we take in each month so we can save for such projects.

Donation tiers

While we accept donations of any size, we do have a tier system with different rewards at each level.

  1. Platinum Sponsor $2000+ per month

    2 hours of support, highest logo placement on homepage and readme and everything in Gold tier.
  2. Gold Sponsor $1000–1999 per month

    Second highest logo placement on homepage and readme, a Thank you tweet from our Twitter account (20,000 followers) and a thank you blog post.
  3. Silver Sponsor $500–999 per month

    Third highest logo placement on homepage and readme.
  4. Bronze Sponsor $200–499 per month

    Fourth highest logo placement on homepage and readme.

ESLint has been critical in helping developers write high-quality JavaScript for years. We love that it catches common issues early and often. With a high level of extensibility, ESLint's ability to let teams enforce custom rules that work for them has been excellent for open-source projects and more. Chrome is happy to sponsor ESLint to help web developers write consistently high-quality code. It's an essential piece of the modern web development toolkit.

Addy Osmani
Addy Osmani Senior Staff Eng. Manager, Chrome

Nx uses ESLint to enforce code quality, library boundaries, and project visibility constraints. ESLint makes Nx more powerful, so on behalf of the community, we're proud to do our part and sponsor ESLint's continued success!

Jeff Cross
Jeff Cross Co-founder and Principal Architect, Nx

ESLint is an extremely useful tool for any JavaScript project. This tool allows us to set up consistent code formatting rules adopted by the whole team from the beginning of the project, greatly facilitates code reviews, and makes it easy to integrate new developers into the team. I know I am not alone in appreciating its flexibility and ease-of-use.

Médédé Raymond KPATCHAA
Médédé Raymond KPATCHAA Technical Architect, Salesforce

Most JavaScript projects directly or transitively depend on ESLint. An Indeed employee nominated ESLint to receive a donation from the FOSS Contributor Fund, and their colleagues clearly agreed. We're happy to support the open source technologies that allow us to develop, protect, and maintain the digital infrastructure that supports our products and helps people get jobs.

Duane O'Brien
Duane O'Brien Head of Open Source, Indeed

ESLint plays a major role in helping us create a safe and consistent experience across a growing number of codebases and engineers. We are grateful for all the open-source projects that are helping us build Contra, and ESLint is the first of many open-source projects that we are committed to back.

Gajus Kuizinas
Gajus Kuizinas Co-Founder / CTO, Contra

Frequently Asked Questions

Everything you need to know about the product and billing. Can’t find the answer you’re looking for? Please chat to our friendly team.

Who receives the money that is donated?

All contributions, whether donated through Open Collective or GitHub, are received by the Open Source Collective, which is a 501(c)(6) non-profit organization. The Open Source Collective acts as a fiscal host for ESLint and keeps track of all donations.

Will I get a record of my donations?

Yes. If you donate through Open Collective, you will receive a PDF receipt via email; if you donate through GitHub, the donation will appear on your receipt or invoice.

Is my donation tax deductible?

No. Even though the Open Source Collective is a 501(c)(6) non-profit organization, the IRS doesn't consider development of open source software to be a charitable activity and therefore doesn’t grant tax-exempt status.

Who decides how the money is distributed?

The TSC makes all decisions regarding who receives the money and how much is distributed.

Can I see how the money is being used?

Yes. By going to our Open Collective page, you can see every expense that has been submitted and paid. All transactions are completely open and publicly visible.

Can I cancel my recurring donation at any time?

Yes. There is no long-term commitment. You can cancel your donation at any time by logging into either Open Collective or GitHub sponsors.

How long does it take for my logo to appear on the homepage, GitHub, and npm package?

The logos on the homepage and GitHub are automatically updated every day so it should take no longer than 24 hours to appear. The logos on the npm package are only updated when we publish a new release, which is typically every two weeks. However, major releases often take several months to complete and during that time logos on the npm package will not be updated.

Where do my logo and URL come from?

We pull the logo and URL from your Open Collective or GitHub profiles, depending on which site you used to donate. You can update these at any time from within Open Collective or GitHub and those changes will be reflected on the homepage and GitHub README within 24 hours. We aren't able to manually override logos or URLs on the site.

Is it possible to make a one-time donation?

Yes. The easiest way to make a one-time donation is through Open Collective, which allows any amount. GitHub one-time donations may have a limit on the amount you can donate.