Hello, thanks for coming back with the additional information.
Could you please enable SonarLint verbose and analyzer logs in the VSCode settings and upload an extract from the SonarLint Output when analyzing the lock_order.js file you mentioned earlier? Maybe there is something off with the analyzer and/or IDE setup on this particular file.
Would it be possible for you to share a minimal reproducer for this issue (a file that reports these issues in SonarQube but not in SonarLint)?
I’m wondering whether this could be linked to type resolution, e.g on SonarQube the analyzer is able to infer that a function in the code is used as a callback, whereas in the current version of SonarLint, type resolution in JS is less precise and can result in such false negatives.