The rule considers protected class methods as public, which contradicts the description in the plugin's docs:

Require explicit return and argument types on exported functions' and classes' public class methods

It's probably a matter of debate whether protected functions should be considered "exported" and I think the best solution would be to have this configurable.

This rule is generally pretty annoying, as it requires putting : void next to methods that don't return anything, but that's perhaps for another issue.

• I have tried restarting my IDE and the issue persists.
• I have updated to the latest version of the packages.
• I have read the FAQ and my problem is not listed.

Repro

{
  "rules": {
    "@typescript-eslint/explicit-module-boundary-types": ["error"]
  }
}

export default class Test {
  testMethod() { // this produces an error, as expected
  }

  protected testMethod2() { // this produces an error, **but it shouldn't**
  }

  private testMethod3() { // this does not produce an error, as expected
  }
}

Versions