@ian - This is still confusing. How come there is an MIT license for overall project but buried under a subfolder (redteam) is an enterprise license?
Of course you have the prerogative to license your product as you wish, but perhaps separating the components based on licensing (open source vs enterprise) as suggested by @xan08_16130 would make much more sense.
I have been pestered by my team members who are hesitant to work with a library that isn't completely open-sourced.
IMHO - current licensing opens a can of worms:
1 - If the parent folder is under MIT license with no explicit mention of any exceptions for subfolder(s) like redteam - it makes a compelling argument that MIT license supersedes any license present in any subfolder.
2 - Redteam subfolder uses imports from rest of the codebase. How does that impact the rest of the project? Are imported code now under enterprise license as well?
Again, we are grateful to you and the team for the great product, but my team as well as many other in the community are apprehensive in our adoption of the product given the mixing of various licensing terms.
Hope you can bring further clarity to this. Appreciate y'alls work!