How to determine which issues are critical in the scanning result of intelliJ-plugin-verifier (version 1.388)?

IntelliJ Platform Plugin Verifier
5

These are not false positives.

  • CefBrowser.getTools() has a dedicated discussion: Accessing DevTools Programmatically in IDEA 2025.3 . Note that the Plugin Verifier is not able to distinguish between production usage and internal debugging usage. All code inside the plugin artifact is considered to be production ready.
  • The same holds for CefRequestHandlerAdapter that is a part of 3rd party library that triggered an incompatible API change.
  • ContentImpl.get()method is simply not available. If you target multiple major API changes, the recommended strategy is to build multiple versions of plugins, compatible with specific target IDEs. Reflection is discouraged, but this usage is not even reflection-based. Furthermore, reconsider this particular API usage, as the Impl suggests that this API is more like internal.
  • Missing com.huawei.deveco: did you declare this dependency as optional in the plugin descriptor?