Skip to main content
Open source dependencies can introduce license obligations that may affect how software is used, modified, or distributed. Reviewing license information helps teams identify potential compliance concerns, verify attribution requirements, and maintain visibility into approved and restricted licenses across the organization. You can view and manage license information across your projects, edit license data, and generate Notice reports for distribution.

​
View licenses

To view licenses:
  1. Select Inventory from the left sidebar.
  2. Select Licenses to view the list of licenses. You can view the license name, OSI approval status, license type, and project count. Licenses list
  3. Use Search license Name to filter the list or search for a specific license.
  4. Use the OSI, Projects, and Type filters to narrow the list.
  5. Select a license row to view the following details:
    • TYPE: License type for the selected license (for example, Permissive, Copyleft).
    • OSI: Whether the license is Open Source Initiative approved.
    • PROJECTS: List of projects that use this license. Expand a project to view the license text for each dependency in that project that uses this license.
    View license details

​
View licenses associated with a project

To view licenses for a specific project:
  1. Select Projects from the left sidebar and select the project for which you want to view licenses.
  2. Select Inventory and select Licenses from the dropdown to view the list of licenses for that project. Licenses list for a project
  3. Select a license to view the following information.
    • Type: Shows the type of license.
    • OSI: Shows whether the license is OSI approved.
    • Full License Text: Shows the license text for the selected dependency version. You can view:
      • Declared License: The license declared by the dependency.
      • Discovered License: The license detected during scanning.
      Click Show full text to expand the full text of either license. Project license details

​
Edit license information

You require Admin role permissions to edit dependency license data. See authorization roles to learn about the different roles Endor Labs offers.
You can edit license information to correct or override license data when scan results or package metadata are incomplete or inaccurate. Editing license information helps you to:
  • Fix misclassified, missing, or unknown licenses so the effective license reflects the expected result.
  • Update copyright, notice text, or license expressions used in generated Notices files.
  • Standardize SPDX identifiers or expressions across projects.
To edit license information from a dependency:
  1. Select Projects from the left sidebar and select a project.
  2. Select Inventory and select Dependencies from the dropdown to view the list of dependencies for that project.
  3. Select a dependency and click Edit.
  4. The Edit Dependency page shows dependency metadata at the top, for example, name, source code location, and package location.
  5. Under Declared licenses and Discovered licenses, click Add License and search for a license to add. You can also edit existing licenses.
  6. Under Copyrights, click Add Copyright to add copyright statements.
  7. Optionally, select Propagate dependency edits to all child namespaces to apply the same changes to related namespaces.
  8. Click Save Dependency to save the changes. Edit dependency licenses

​
Generate a license notice report for a project Beta

A license notice report lists open source dependencies with their license texts, copyright notices, and source code locations. You must include a license notice report when you distribute software that contains open source dependencies.
To generate a license notice report from the command line, see license-notice-report generate.
To generate a license notice report:
  1. Select Projects from the left sidebar and select the project for which you want to generate a report.
  2. Click Export > Notice Report. Generate Notice report
  3. Choose the output format for the report. Available formats are TXT and Markdown.
  4. Optionally, enter a Report Name. This sets the title printed inside the generated notice document. It doesn’t change the report’s name on the Reports page, which Endor Labs generates automatically.
  5. Under Select Packages, choose one or more packages for the report. If you don’t select any packages, the report includes all packages in the project. Test dependencies are excluded. Projects can contain multiple packages with several manifests. Selecting more than one package generates a single combined report.
  6. Choose the following filters to refine the data included in the report.
    • Multi-Licenses: Filter based on which license to use when a dependency has multiple licenses.
      • Select All to include every license associated with the dependency.
      • Select Most Permissive to include only the most permissive license.
    • Type: Filter based on whether the license was declared by the dependency or discovered during scanning.
      • Select All to include both declared and discovered licenses.
      • Select Declared Only to include only licenses declared by the dependency.
      • Select Discovered Only to include only licenses discovered during scanning.
    • License Category: Select one or more license categories, such as Permissive, Copyleft, or Public Domain, to include in the report. By default, all license categories are included.
    Click Reset filters to clear these back to their defaults.
  7. Toggle Include Copyright information to include copyright statements in the report. When you include copyright information, the Components section of the report lists the copyright statements found for each dependency, and includes dependencies that have copyright statements but no license information. Otherwise, Endor Labs omits those dependencies so the report contains no empty entries.
  8. Select Use custom disclaimer to the notice file to enter disclaimer text to show at the top of the notice file. You can enter up to 8,192 characters of disclaimer text.
  9. Click Create Report to generate the report.
Generate license notice report for a project
See License notice report for multiple projects or packages to generate a license notice report for multiple projects or packages.

​
View license notice reports

To view license notice reports:
  1. Select Reports from the left sidebar.
  2. Select a report to view its details such as file format, license type, multi-license policy, copyrights setting, custom disclaimer, and package scope.
  3. To download a report, click the three vertical dots and click Download.
  4. To delete a report, click the three vertical dots and click Delete.
See Reports for more information on managing reports.

​
License notice report structure

Every license notice report contains three sections. The Header identifies the report, Components lists your dependencies, and Licenses holds the license texts. TXT and Markdown reports carry the same content. The following template shows the layout of a report.
The following examples show a trimmed report for two dependencies in each output format.