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

Our scanning tool tags the component as open and misses the field-of-use restriction

The scanner recognizes the license name in its database but classifies the whole entry as unrestricted because its rule set has no category between open and proprietary. Anyone trusting the automated report would never learn about the commercial carve-out written into the actual terms. We now attach a manual note every time this component shows up in a scan.
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.