Individual

Open Source License Report

Risk removed

Catches the legal risk of non-compliant open-source licenses that could force you to disclose source code or pay damages.

Launch price $149 $119

Ends Dec 4, 2026 (Korea time)

Final price in USD. Local taxes are your responsibility.

Order assessment
Open Source License Report

Inspection scope

  • Licenses
  • SBOM (SPDX 2.3)

Evidence, remediation guidance and a digitally signed PDF for the selected scope

Within 24 hours after submission

Required evidence

  • Source repository or ZIP

Full refund before analysis starts; after it starts, no refund for change of mind (full refund if we fail to issue the report within the turnaround time for reasons on our side).

Who this is for

  • Companies preparing for investment or acquisition due diligence, or a large-enterprise supplier review, that want to resolve open source license issues in advance
  • Teams concerned about receiving a license violation notice while running their service
  • Situations where you need to submit an SBOM (software bill of materials)

What we check, and how

  • License classificationWe identify the open source components in your code and their licenses, separating permitted licenses (Pass) from strong copyleft licenses such as GPL and AGPL that can lead to source disclosure obligations (Fail) (ScanCode, ORT).
  • Including code outside package manifestsCode copied in directly does not appear in package manifests. Because we inspect the license notices in every file, we also verify the licenses of components that package manifests miss.
  • SBOM generationWe also provide an SBOM in the international SPDX 2.3 format.

What the report includes

  • A summary for the CEO: whether any license could become an issue in due diligence or supplier reviews
  • Evidence list: component / license / file path
  • SBOM (SPDX 2.3), plus a digitally signed PDF with an authenticity-check hash

How it works

  1. Upload source code: a ZIP file or a read-only repository
  2. Analysis in a closed network, with no external transfer
  3. Within 24 hours after submission: report issued
  4. 1 free rescan(s) within 30 days after you fix the issues

Frequently asked questions

Is it automatically a problem if GPL code is mixed in?

It depends on which module uses it and how. The report shows the component and file path as evidence; a final legal judgment requires review by a legal professional.

What is an SBOM used for?

It is a standard format you can submit as-is when investment or M&A due diligence, or a large-enterprise or public-sector supplier review, asks for a list of software components.

Is it safe to hand over our source code?

Source code is analyzed only in an isolated, closed-network environment and is never sent to an external LLM. Submitted source ZIPs, repository links and read-only tokens are automatically deleted once the assessment is complete, and the deletion is logged as evidence. If source code leaks through our system, we compensate 100 times the amount paid for that assessment (Terms of Service).

What do we receive?

A digitally signed PDF report that combines a one-page summary for the CEO with file- and line-level evidence your development team can act on directly. The report carries an authenticity-check hash, so it can be submitted to third parties.

Can we get a refund?

You receive a full refund before analysis starts. Once analysis has started, refunds are not available for a change of mind, but you receive a full refund if we fail to issue the report within the turnaround time for reasons on our side.