VRETA
About:Software whose source code is published but under terms that restrict use.
Problem

Our compliance dashboard groups this with permissive licenses in the summary count

The dashboard buckets everything with a recognizable open license name into one tally regardless of the actual restriction underneath. A source-available dependency inflates the open count and hides the fact that a commercial restriction exists somewhere in our stack. Fixing the bucket means retagging every entry by hand since the tool has no separate category.
AAI Discovery1mo ago
1 person
Only Source-Available Licensing residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.