kotlin:S107 still reports issues on Jetpack Compose @Composable functions in SonarQube Cloud

SonarQube Cloud
,
1

Hi,

I’m opening a new topic because the previous discussion about this issue is now older than two months:

Previous topic:

We are currently using SonarQube Cloud, and kotlin:S107 is still reporting issues on functions annotated with Jetpack Compose @Composable.

For example:

@Composable
fun MyComponent(
    param1: String,
    param2: String,
    param3: String,
    param4: String,
    param5: String,
    param6: String,
    param7: String,
    param8: String,
) {
    // ...
}

SonarQube Cloud reports:

This function has 8 parameters, which is greater than the 7 authorized.

kotlin:S107

Our Kotlin Quality Profile inherits from Sonar way, and the rule is configured with the default:

Max: 7

We have not overridden the rule.

From the previous discussion, my understanding was that @Composable functions were supposed to be ignored by kotlin:S107.

In particular, a SonarSource team member mentioned in March 2026 that the change should already be available in SonarQube Cloud.

However, we can still reproduce the issue today.

Expected behavior

Functions annotated with:

androidx.compose.runtime.Composable

should not raise kotlin:S107, while regular Kotlin functions should still use the configured maximum number of parameters.

Actual behavior

@Composable functions are still analyzed by kotlin:S107 and raise an issue when they have more than 7 parameters.

Could you please confirm whether support for ignoring @Composable functions was actually released?

If it was released, is there any additional configuration required on SonarQube Cloud?

If it was not released, is there an issue/ticket we can follow for this change?

Thanks!

2

Hey @sirambd, welcome to the Community! Although it’s good practice to not re-open old threads, in this particular case it would have been justified because the fix hasn’t actually been released yet. Perhaps it was not very clear in the original thread, sorry for that :sweat_smile:

The ticket that is tracking this fix is private and you wouldn’t be able to see it, however, I can tell you that work on this false positive seems to be in progress and is targeting the next release of the Kotlin analyzer. I’ve let the devs know about this thread, but also feel free to “watch” (button at the bottom) the other thread in case they announce it there.

3

Hi @sirambd,

Thanks for your feedback! This issue was finally fixed and will be available soon, after release.