-
-
Notifications
You must be signed in to change notification settings - Fork 576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Two proprietary-license rules generate false positive detections #3504
Comments
Our general approach to dealing with these kinds of detections (which should really be clues) and similar
The question is whether this is a seperate case from the The difference will be: Earlier:
After marking as clue:
|
Reference: #3504 Signed-off-by: Ayan Sinha Mahapatra <ayansmahapatra@gmail.com>
This was fixed, closing! |
A recent scan of an FFmpeg project returned a composite license expression that included
AND proprietary-license
in the various licenses, and that was totally incorrect, as there was no object in the codebase under any proprietary license. The culprits are two rules that are simply getting clues from configuration file documentation, and I think that these rules should simply be deleted.proprietary-license_489.RULE
proprietary-license_490.RULE
The rules are simply finding the configure instructions that the FFmpeg authors provide to anyone that wants to build FFmpeg to include proprietary code (which results in a non-redistributable build, since that is not compatible with GPL, but that's another story). But SCTK is interpreting these rules to mean that there is some software object in the codebase under a "generic" proprietary-license, when there is actually no such object in the codebase.
The text was updated successfully, but these errors were encountered: