https://promptfoo.dev/ logo
x
I see that promptfoo is under MIT license, however the repository has the redteam folder under source which is under enterprise license. This creates an issue from overal licensing perspective. Is there a plan to separate out redteam component ?
i
this change was reverted
p
@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!
i
all good questions. the main reason we have adjusted the red team license is because certain companies continue to copy/steal the red team source code without attribution (in violation of the MIT license, let alone any proprietary license). Our intent is to make this freely available and open source. We want security practitioners to use this to their hearts' content. We don't want other companies reselling our work without attribution. Hate to see others exploit it directly for commercial gain, but we will likely just remove the subdirectory license and keep it all MIT.
x
Thank you. My company flagged it , and unless we have a clear license terms upfront, using it will be difficult as code scanners within company will flag it. Again, can you move redteam to a different repo ? that way you can best of both ?
Yup - got flagged on the latest build with this URL - https://github.com/promptfoo/promptfoo/blob/0.103.11/src/redteam/LICENSE.md
i
@xan08_16130 Thanks for following up. That license has been removed from the next release
x
Thank you. Again appreciate the hard work y'all put in.
i
this is released in 0.103.14
x
Ah, it got flagged again - not sure if this is something that can be addressed. /* * The prompts used by this CLI are licensed under the AGPL-3.0 license and are * dynamically downloaded from Github. For details, see * https://github.com/elder-plinius/L1B3RT4S/blob/main/LICENSE. */ here - https://github.com/promptfoo/promptfoo/blob/ce32d180105977b785b2adb8ddd511fb0d097a64/src/redteam/plugins/pliny.ts#L2
i
I think this is a false positive - Promptfoo doesn't contain any APGL-licensed code. If you don't use the
pliny
plugin, those URLs won't be accessed
x
but the presense of that text, flags the package.
Will it be possible to remove it ? sorry for the trouble, but need to take a call if this library can be used within my company OR we pivot. Again, sorry for being pushy, but wanted to know if it is possible.
i
this will be removed/updated in the next release
x
thank you, it worked