OSS Table Warning Message

You can identify issues that need to be reviewed through the Warning Message in the OSS Table.

  • Meaning of Warning Messages by Color
    • Red : Requires correction; review request or confirmation is not possible. Review and modify as necessary.
    • Blue : Review request and confirmation are possible, but further review is required. Please check carefully.
    • Gray : Informational message; no specific action is required.

Review Items According to Warning Messages

Common

Column Warning message Description Things to review
OSS Name, License Required
  • Required field, so you must enter a value.
 -
Source Path Format Warning
  • File format is not correct.
  • Make sure the path or file is entered correctly.
OSS Name New open source
  • New OSS that is not registered in the FOSSLight Hub.
  • If OSS List of the FOSSLight Hub has the same OSS but different name, change OSS Name to the name registered in the FOSSLight Hub.
  • However, if there is no OSS in the FOSSLight Hub, no correction is necessary. (In this case, the Download location and Homepage column must be filled in.)
OSS Name Deactivated
  • This is a legacy OSS registered in the FOSSLight Hub but deactivated.
  • Please fill in the Download location of the OSS used.
OSS Name Required OSS Name
  • You should enter the OSS name.
 If the license contains source disclosure obligation, clear information for the OSS is required. Check the OSS and fill in the OSS Name.
OSS Version New version
  • New Version that is not registered in the FOSSLight Hub.
  • Check if you can download the source code for that version from Download Location.
  • In the following cases, leave the version blank.
    • If the version is not officially distributed. (e.g., unspecified)
    • In the case of OSS where the version is not separately managed.
License Declared : [License of OSS]
  • OSS is registered with another license in the FOSSLight Hub, or a license type other than Permissive is missing among the OSS licenses registered in the FOSSLight Hub.
  • Check whether a written license is included or an unwritten license is not included.
License New license
  • New License that is not registered in the FOSSLight Hub.
  • We recommend that you request a license review in advance through CLM.
License Recommended : [License of OSS]
  • It is a dual license and the license other than the license generated by auto-completion is written.
  • To select a more permissive license, consider changing to the license displayed in recommended.
License Dual : Put one license
  • Although it is a dual license, both licenses are written as if both are used.
  • In case of Dual License, you can choose a permissive license. Please fill in only the selected licenses.
License Put OSS name or one license
  • Although the OSS Name is - or blank, multiple licenses are written in one row.
  • If the OSS Name is - or blank, please separate the rows for each license.
Homepage The address should be started with www or http:// or https://
  • Homepage format is not correct.
  • Make sure the Homepage is entered correctly. Write with addresses starting with www, http://, or https://.
OSS Version, License Format error
  • Contains line separator characters.
  • Please make sure that it does not include a line separator character.
  • If you want to write multiple lines, please add Row.
Download location, Homepage Different from DB
  • The URL you entered is different from the URL registered in the FOSSLight Hub.
  • Please review whether it is the same OSS registered in the FOSSLight Hub.
  • In case of other OSS, please separate OSS Name from those registered in the FOSSLight Hub.

BIN, BIN(Android) Tab

Column Warning message Description Things to review
Binary Name Same: [OSS Name] [OSS Version] / [License] If OSS Name, License is different. OSS information is displayed for the same binary stored in Binary DB.
  • After checking the information about same binary stored in Binary DB, supplement OSS Name / Version, License information if necessary.
Same : / [License] If only the License is different.
Same : [OSS Name] [OSS Version] If only OSS Name is different
Same : [OSS Name] [OSS Version] Only when the OSS Version is different or the license is the same and the license type is Proprietary or Proprietary Free.
Similar(TLSH distance) : [OSS Name] [OSS Version] / [License] If OSS Name, License is different. OSS information is displayed for similar binaries stored in Binary DB. (The parenthesis shows the TLSH distance value.)
  • After checking the information about similar binary stored in Binary DB, correct OSS Name / Version, License information if necessary.
Similar(TLSH distance) : / [License] If only the License is different.
Similar(TLSH distance) : [OSS Name] [OSS Version] If only OSS Name is different.
Similar(TLSH distance) : [OSS Name] [OSS Version] Only when the OSS Version is different or the license is the same and the license type is Proprietary or Proprietary Free.
Modified(TLSH distance) : [OSS Name] [OSS Version] / [License] If OSS Name, License is different. OSS information is displayed (gray) for binary with the same name but less similarity (TLSH distance> 120) in Binary DB. (The parenthesis displays the TLSH distance value.)
  • After checking the information about the binary with little similarity stored in Binary DB, correct OSS Name / Version, License information if necessary.
Modified(TLSH distance) : / [License] If only the License is different.
Modified(TLSH distance) : [OSS Name] [OSS Version] If only OSS Name or OSS Version is different.
Matched In case of same or similar binary. In the binary DB, data with the same Binary Name, OSS Name, OSS Version, and License exists. -
Modified(TLSH distance) In case of binary with the same name but less similarity
New There is no binary with the same name in Binary DB. -
  • Be careful when inputting information because it is a new binary that has never been registered in Binary DB.
Notice NOTICE should be "ok" in case OSS is used The binary must notify the copyright notice and license, but NOTICE.html does not contain the value written in the Binary Name column. -
  • You should add the used Binary Name and its License text for that Binary to the NOTICE.html file.
Found binary in NOTICE.html The binary does not need to notify the copyright notice and license, but NOTICE.html contains a value written in the Binary Name column. -
  • You need to make sure that the NOTICE.html does not contain any notices that should not be noticed such as Other proprietary license (= Not an open source license).