endor-license

To scan dependencies for license compliance, this Skill analyzes manifest files like package.json and go.mod across languages to surface license types, identify restrictive categories, and produce remediation guidance.

Dependency license compatibility analysis identifies whether open-source licenses in your project conflict with organizational policies, which is needed before releasing software to avoid legal risks from restrictive or copyleft terms.

You can check your dependency tree for strong copyleft licenses by running an Endor MCP license scan on your repository, which flags restrictive licenses and compatibility issues requiring immediate action.

Yes, this license scan works with Go modules and Node lockfiles by parsing manifest files like go.mod and package.json to extract dependency details and assess licensing across multiple programming languages.

The best way to enforce software licensing policies is to scan dependency trees to identify license risks, then apply the generated remediation guidance to restrict incompatible or unknown licenses before deployment.

For unknown or restrictive dependency licenses, the scan provides policy guidance recommending specific actions to resolve compatibility issues and align your project with organizational licensing requirements.