Our last analysis on main was 11/23. I believe I know which commit is causing this failure, but I’m not able to see any specific error messages so it’s not clear what we need to do to fix this.
1 Like
Hello Austin,
Thanks for reporting this. From what we could see on our side, it seems to come from the JS security analysis. What the problem is exactly is hard to pinpoint without a reproducer though.
Would you be willing to try to reproduce the analysis locally and share the yourProject/.scannerwork/ucfg2 folder with us privately? That is the basis used for the security analysis and would be of great help to us to investigate and understand the root of the issue.
In the meantime, you can disable the rules related to the JS Security analyzer as a temporary workaround (these are the rules: S2076, S2083, S2631, S3649, S5131, S5144, S5146, S5147, S5334, S5696, S5883, S6096, S6105, S6287, S6350). This is definitely not ideal, but would at least let you run the analysis for all the other rules.
Best,
-Christophe
@czurn apologies for the delayed response. We were able to figure this out. A commit moved some of the files we had been excluding, which put us over the threshold for our LOC. Once we updated the exclusions the analysis was able to successfully run.
Hello Austin,
Ok, great. Glad to hear that you were able to resolve the issue on your side 
And thanks for letting us know!
Best,
-Christophe
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.