[5Qn8mNbc2FNCiVV]

I don't see the issue this attempts to solve. The one thing mentioned is caching, but you shouldn't mix caches of different users (or user groups) anyways if f.e. you encode a user's access privilege in the query. This however doesn't even do it and always loads the data, so instead of attempting to cache the result of the query after access is checked, just cache the result of the query.

I checked the library and thought this would be something more revolutionary that I missed, but sadly it's "just ok". At least for me it doesn't come close to what f.e. https://casl.js.org/v6/en/ provides or you know, me just having the access control encoded into a where-clause