endor-license

Identifying copyleft exposure requires inspecting project manifests such as package.json or go.mod and the full dependency tree. This surfaces license details and risk levels, producing a structured inventory with remediation guidance for governance.

Checking license compatibility involves analyzing the full dependency tree from your manifests to surface license details and risk levels. This produces a risk-aware report with actionable guidance to align licenses with your project aims and risk tolerance.

Generating a license inventory involves scanning your manifests and the full dependency tree. The analysis surfaces license details and risk levels, providing a structured report with remediation guidance for policy enforcement and governance workflows.

Yes, license analysis works with Go modules and Node.js by inspecting manifests like go.mod and package.json. It analyzes the full dependency tree to surface license details and risk levels for your specific project context.

You need to run a dependency license risk check when evaluating a new dependency or enforcing compliance policies. It surfaces license compatibility and potential copyleft obligations by analyzing your project manifests and the full dependency tree.

Identifying copyleft exposure relies on inspecting manifests like package.json and go.mod and the full dependency tree. The resulting risk-aware report provides remediation guidance, but policy enforcement requires integrating these outputs into your governance workflows.