Thanks for the input! You're right, the OSS license, active committers, and accepting outside PRs are key points. We'll include them next time. Appreciate the suggestion!
Stars don't really say that much, for me it's a bookmark for projects I might (but probably won't) take a closer look at later. Don't trust them and do your due diligence.
In my experience no/low code tools are fine until they are not, and until you follow the narrow path.
It's highly likely you'll have some requirements that cannot be satisfied by the tool.
If you are a dev, code is the best interface. If you are not a dev, don't want to be one, and you can shoulder the risks, sure go ahead.
If you are a manager and want to push a no code tool, you will regret it and your team will resent you.
Balancing usability with control is an art. It's crucial to offer tools that are accessible yet robust enough to not leave users feeling like they've lost control over the customization and scalability of their projects.
Also important are number of active committers and if they actually accept outside PRs.