Static code analysis with sonar for rules, hooks and actions

Help
,
1

We want to do a static code analysis with sonar for all code that we are using as part of auth0 including custom login page, rules, hooks.
I was getting and error and raised an auth0 ticket but they said that they cannot give guidance for external tools.
Has anyone done this? any inputs is appreciated.

Am getting a parser error when trying to scan auth0 rules.

05:08:33.405 DEBUG: Analyzing file: file:///home/vsts/1/s//myrule.js
05:08:33.411 DEBUG: Analyzing file “/home/vsts/1/s/myrule.js” with linterId “default”
05:08:34.031 DEBUG: Failed to parse /home/vsts/1/s/myrule.js with TypeScript parser: Identifier expected.
##[error]05:08:34.249 ERROR: Failed to parse file [myrule.js] at line 1: Unexpected token (1:9)

2

Hey there!

Added a few tags to your questions so that others can find it more easily.

3

Hey there!

As this topic is related to Rules - Hooks - Actions, I’m excited to let you know about our next Ask me Anything session in the Forum on Thursday, January 18 with the Rules, Hooks and Actions team on Rules & Hooks and why Actions matter! Submit your questions in the thread above and our esteemed product experts will provide written answers on January 18. Find out more about Rules & Hooks and why Actions matter! Can’t wait to see you there!

Learn more here!