In the early days, context.py used the wordlists in the wfuzz repo. We didnt see enough reason to keep the wordlist list of wfuzz, and settled for context.py utilizing the user provided wordlist.
But looking at the current state, theres a good chance context.py would be noticably more effective with dedicated wordlists. The wfuzz wordlists are far from optimal for context.py, which means we should look for alternative resources. But it may be worth it to do so, even if we include them just for context.py
Optimally:
One repository with wordlists for all common extensions we are looking for in context.py, with the wordlists being reasonable in size (not above ~10k lines)
In the early days, context.py used the wordlists in the wfuzz repo. We didnt see enough reason to keep the wordlist list of wfuzz, and settled for context.py utilizing the user provided wordlist. But looking at the current state, theres a good chance context.py would be noticably more effective with dedicated wordlists. The wfuzz wordlists are far from optimal for context.py, which means we should look for alternative resources. But it may be worth it to do so, even if we include them just for context.py