FOSSLight Report
- FOSSLight Report is a template used by FOSSLight Hub and FOSSLight Scanner to identify the usage status of Open Source per project, and is also referred to as an ‘OSS Report'.
- Version 3.3: Fosslight_Report.xlsx
Sheet Structure
Project Info Sheet
- Fill in the project information.
3rd Party Sheet
- If the project includes software provided by a 3rd party, obtain the OSS Checklist from the 3rd party to identify what Open Sources are used.
- The identified Open Source information is registered in the 3rd Party menu of FOSSLight Hub and is collected in the Project > Identification > 3rd Party tab.
- When the FOSSLight Report is exported from FOSSLight Hub > Project > Identification, the information registered in the 3rd Party tab is automatically filled in the "3rd party" sheet. Therefore, do not manually fill in the "3rd party" sheet.
DEP Sheet
- Upload the Dependency analysis results.
- FOSSLight Dependency Scanner can be used to automatically generate "DEP" sheet.
SRC Sheet
- Fill in the Open Source information included per Source Code.
- FOSSLight Source Scanner can be used to automatically generate the "SRC" sheet.
BIN Sheet
- Fill in the Open Source information included per Binary.
- FOSSLight Binary Scanner can be used to automatically generate the "BIN" sheet.
BIN(Android) Sheet
- Fill in the Open Source information for Android Platform Project and Yocto Project.
- FOSSLight Android Scanner and FOSSLight Yocto Scanner can be used to automatically generate the "BIN(Android)" or "BIN(Yocto)" sheets.
- For Android Platform and Yocto-based models (such as phones and TVs), the DEP, SRC, and BIN sheets do not need to be filled in.
BOM Sheet
- BOM (Bill of Materials) is generated by collecting the Open Source information from each sheet in the FOSSLight Report.
- As the BOM is automatically filled in when exporting the FOSSLight Report from the Project in FOSSLight Hub, manual editing is not necessary.
Sheet Content Creation
By using FOSSLight Scanner, DEP, SRC, and BIN sheets can be automatically generated at the same time. However, you must manually check and supplement any missing or inaccurate information.
Common Requirements
| Column Name | Description |
|---|---|
| OSS Name | • Fill in the OSS Name based on the name specified on the website from which the Open Source was downloaded. • Utilize the Pre-Review feature to identify the OSS Name through download location information. • If the License text exists but the Open Source name or origin is unclear, fill in the OSS Name with a hyphen ("-"). – Fill in all other information such as License and Copyright. • If no Open Source was used, fill in a hyphen ("-") in the OSS Name field. – This applies only if the License is Permissive. For Copyleft Licenses like GPL or LGPL, accurately confirm the OSS Name and origin to determine the scope of source code disclosure. |
| OSS Version | • Fill in the version of the Open Source used. |
| License | • If multiple Licenses apply to a single Open Source, separate them with commas (","). • If no Open Source was used, fill in "LGE Proprietary License", or "Other Proprietary License" if developed by a third party. |
| Download Location | • Fill in the URL where the Open Source of the specified OSS version can be downloaded. |
| Homepage | • Fill in the official website URL of the Open Source project. |
| Copyright Text | • Fill in the copyright information of the Open Source. |
| License Text | • If the License is not registered in FOSSLight Hub, fill in a link to the original License text or the License text itself. |
| Exclude | • Check this box if the Open Source is not included in the software(including products) to be distributed. |
Sheet-Specific Content Creation
Project Info Sheet
- About the Report: Fill in the author/department and date of creation.
- About the Project: Fill in the information about the development project.
Detailed Content Creation
| Item | Description |
|---|---|
| Project Name | • Fill in the name of the project. If the model name and project name are the same, use the model name. |
| Project Version | • Fill in the version of the project. Leave blank if there is no version information. |
| Operating System | • Select the operating system of the project (e.g., Android 7.0, webOS 3.0, Linux 3.4, iOS Application). |
| Distribution Type | • Choose the distribution type of the project. • General Model: For general B2C models • Transfer in-house: For internal transfers • B2B: For B2B models • Preceding Software: For pre-development without planned distribution • Self-Check: For internal review and pre-verification, not for external distribution |
| Network Service Only? | • If the project is a network service (e.g., Web Service), select 'Yes'. |
- About OSC Process: Fill in the information about the Open Source Compliance(OSC) process.
Detailed Content Creation
| Item | Description |
|---|---|
| Distribution Site | • Select the open source distribution site where the OSS Notice will be registered. (Reference: LG Open Source Site) • Mark as "N/A" if not distributed through a distribution site. |
| OSS Notice | • Select the type of OSS Notice. (Reference: OSS Notice) • Generally, select "General". • If the OSS notice is generated automatically on the project's development platform, select "Platform-generated". |
BIN Sheet
- If multiple Open Sources are used in one Binary, add separate rows for each Open Source.
- Source or Binary Path: Specify the path to the source code or binary, depending on the delivery form (Source Code or Binary).
BIN (Android) Sheet
- Source Path: Fill in the source code path of the Binary. If verification is difficult, provide the reason in the Comment column.
- NOTICE: Follow the results from the FOSSLight Android Scanner without manual modifications.
- If multiple Open Sources are used in one Binary, add separate rows for each Open Source.