The OSS maintainer should clearly, upfront, preliminarily, outline how do they govern the project: how much are they open to change the project's core values, how responsive on average will they be in terms of opened issues and PRs, roughly how often would they engage in technical architectural debates -- stuff along those lines.
I feel many people get toxic if they had unrealistic expectations -- and that's of course not okay.
But IMO the OSS maintainers can be a little more preliminarily proactive in managing expectations from earlier stages.