CodeThreat - Knowledge Center
CodeThreatGithub
  • Latest
    • v2409 Cloud Upgrades, Repo Monitoring, Path Exclusion, and New JS/TS Rulesets
  • Product Updates
    • v2402 GenAI, Sarif and New Language Supports
    • v2401 SCA Release
    • v2311.30
    • v2310.29
    • v2309.30
    • v2308.30
    • v2307.25
    • v2306.26
    • v2305.26
    • v2304.23
  • Privacy Policy
  • Terms of Service
  • Company Handbook
  • Usage Guide
    • API Documentation
    • CT Server Installation
      • Deploy with Docker
      • Self-Hosted Server Setup
      • Installation
    • Introducing CodeThreat
    • Create a CodeThreat Account
    • Quick Start & Scan
    • HomePage
    • Projects
      • Overview
      • Scans
      • SCA(Software Composition Analysis)
      • Licences
      • Dependency Tree
      • Project Structure
      • Report
    • Issues
      • Issue List
      • Issue List Filter
      • Issue Detail
    • Integrations
      • Azure
      • Github
      • Gitlab
      • Jira
    • CI-CD Integrations
      • GitHub Actions
      • Jenkins
      • Gitlab
      • Bamboo
      • Azure
    • Notifications
    • Settings
      • General
      • SMTP
      • License
      • OAUTH Apps
        • Azure
        • Github
        • GitLab
      • Organizations
      • Scan Policy
      • Users & Groups
      • Notifications
      • Access Token
Powered by GitBook
On this page

Was this helpful?

  1. Usage Guide
  2. Projects

Licences

PreviousSCA(Software Composition Analysis)NextDependency Tree

Last updated 1 year ago

Was this helpful?

  • Each license entry will typically include the license name and may have a link or arrow to expand for more details.

  • Review the licenses to ensure compliance with legal requirements and project standards.

  1. Identify Licenses: Each license listed represents the legal terms under which a component or library is used. Ensure that you recognize each license type present in your project.

  2. Expand License Information: If more information is available for a license, click the arrow or link associated with the license to view details such as the full license text, obligations, and compatibility with other licenses.

  3. Check Compliance: Verify that the use of each component or library is in compliance with its license terms. Pay attention to restrictions or obligations like attribution, redistribution, or modification.

  4. Resolve License Issues: If potential license issues are identified, such as incompatible licenses or use that is not in accordance with the license terms, take the necessary steps to resolve these issues. This may involve replacing a component, modifying the usage terms, or obtaining additional permissions.

  5. Document License Compliance: Keep records of license compliance checks and resolutions to ensure that the project documentation is up