license-compatibility-auditor

To audit OSS license compatibility, resolve direct and transitive dependency metadata against SPDX, OSI, FSF, and Blue Oak sources to surface identifiers and flag compatibility concerns. This generates an evidence-backed compliance report for your project.

SPDX identifier resolution maps transitive dependencies to standardized license tags using live metadata sources. It tracks per-package evidence and license-change events to clarify your project's compliance posture.

Yes, you can generate SBOM-ready exports that include per-dependency reporting with CLA-flag detection. The analysis is deployment-mode aware, surfacing configurations that commonly trigger legal reviews.

Yes, license-change tracking works with ClearlyDefined metadata to monitor dependency license shifts. It applies live data from SPDX, OSI, FSF, and Blue Oak to provide evidence-backed per-package reporting.

You need a deployment-mode aware license compliance audit when your project's distribution context triggers different legal review thresholds. This analysis flags specific configurations and compatibility concerns based on how you deploy.

The best way to detect FSF compatibility issues is applying live FSF compatibility metadata across your direct and transitive dependencies. This surfaces evidence-backed compatibility concerns and flags packages requiring legal review.