Looks really cool, although it's a shame the description isn't a bit more "plain language" - a simple summary of what it is intended for, before going into jargon would help people realise why it's valuable. The fact it uses a cache isn't immediately important: I doubt anyone is saying "I hope I can find a solution which uses a cache", they'll be saying eg "I'm struggling with QA, what can streamline it?".

The paper's introduction section is more useful, but I wonder if people will get that far. Likewise the repo screenshot is useful but it's way down the README page.

Anyway, these are just well intentioned comments. It's easy to lose track that potential users won't get what you've been building until you pitch it in their terms.