you have to be logged in to see a plugins 'used by' and 'works with' why?

I would say because that is how this site works, what is the problem ?

It would be better if the site worked correctly, no?

JimDeadlock

It would be better if the site worked correctly, no?

What is wrong in having to log in to use the site, any other site you go to requires a log in to access the sites functions, So as i said what is the problem and what is not working correctly ?

If you had to log in to view the site at all that would be understandable, but that's not the case. If you are logged out you can still see the plugin page, so you will assume that you have all the info and then be confused when your plugin doesn't work because of a missing dependency that you are not aware of because the info was invisible on the plugin page. It's clearly a bug.

TLDR: a logged-out user should be able to see all or none of the info, not a partial version of it.

pookins

I would say because that is how this site works, what is the problem ?

much thinking, many logics, so arguments, wow

When the website was developed performance was the primary goal. I can't speak for that dev that wrote the site but I'm assuming it might have something to do with extra database queries. When you're not logged in there is a lot of features that get restricted and throttling and rate limiting happens.