GCI Rules not being triggered

[VasilisTako]

Current Behavior

Installing the plugin on sonar and configuring a newly created quality profile on a local project doesn't trigger any GCI rule.
I've tested running the sonar server with the github release jar of version 2.1.0 and manually building it too from the repo and the result is the same.

To force the trigger of the rule GCI9, as an example, i added on my ts an import * ..... and still not getting any result.

Here some screenshots:

1. TS quality profile (with the 15 custom rules from the plugin):

2. Project assigned profiles (the CSS and HTML were added by sonar after the first scan):

3. Reported Issues tags (no creedengo present)

Expected Behavior

GCI rules being triggered correctly.

Steps to Reproduce

1. Added the plugin on sonar extensions and runned the instance
2. Created a new quality profile for TS and a JS adding the plugin custom rules (separated)
3. Created a new local project on sonar
4. Assign to the local project my newly created TS quality profile from creedengo rules.
5. Add an import * ..... to one of the file that will be analyzed.
6. No Gci rule have been triggered on the report.

Failure Logs

No visible failure logs

creedengo-javascript Version

2.1.0

SonarQube Version

Community Build v25.3.0.104237

Additional Information

Here the sonar-project.properties for the sonar-scanner run:

sonar.host.url=http://localhost:9001
sonar.login=sqp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
sonar.projectKey=test-creedengo-js
sonar.projectName=test-creedengo-js
sonar.projectVersion=1.0

sonar.sources=src
sonar.language=ts
sonar.exclusions=**/*.spec.ts,**/node_modules/**,**/e2e/**

In addition i've installed on this moment the js, java and python versions of creedengo plugins. The last 2 trigger GCI rules correctly during the scan.