license-audit-tool

To audit dependencies for GPL and AGPL license risks, parse dependency manifests across ecosystems to collect metadata, classify licenses into Safe or Restrictive categories, and generate a Findings Summary with remediation recommendations.

Yes, you can scan transitive sub-dependencies for restrictive licenses in a monorepo. The audit tool applies to both monorepos and multi-language projects to identify GPL/AGPL contamination across all transitive dependency layers.

The best way to prevent GPL contamination in multi-language projects is to run a comprehensive license audit that identifies restrictive licenses in dependencies and produces risk scoring alongside actionable remediation guidance.

License classification separates safe dependencies from restrictive ones by parsing metadata from manifests and categorizing licenses into Safe (MIT, Apache, BSD) and Restrictive (GPL, AGPL) groups to flag transitive risks.

Yes, the license audit tool works with multiple package ecosystems and manifest formats. It parses dependency manifests across various ecosystems to collect license metadata and produce a comprehensive audit for monorepos and multi-language projects.

Remediation recommendations for non-compliant dependencies are provided in a Findings Summary that outputs actionable guidance to resolve identified restrictive GPL or AGPL license risks found during the manifest scan.