Well yes, the problem is always communication and clear labeling on ANYTHING. Even food and beverage packaging got regulated to a degree that may be annoying to a layman. Doing something without context in the open WILL cause people to speculate. Imagine if you didn't see a sign about road work ahead and the traffic slows to a crawl. Would you think there is an accident? Or vice versa. So clear labeling about it being an experiment is a good idea from the start for any project IF AND ONLY IF the developer cares.

I for example didn't care if my FOSS library got used. I don't care if people criticize my language of choice or my code style. I license my stuff in MIT precisely because I couldn't care less about anything my software that I decided to be opened is doing. My open source model is I work for my own use case. I will not consider other use cases. It may contain vulnerability with certain configurations, so be it as long as I don't use those configurations. I will fix it if I feel like it. We need to normalize open source as an individual pet project again. If people depend on said pet project, that's on them, not the maintainer.