Know which licenses ship with your software.
Review the licenses in your direct and transitive dependencies, understand their obligations, and check them against your organization’s policy—with the supporting evidence attached.
See the evidence behind each detected license.
Package-registry metadata does not always tell the whole story. Farion inspects the license files and contents shipped with a dependency so you can review what the detected license is based on.
Understand what a dependency asks of you.
Review attribution, notices, source-disclosure, and redistribution obligations alongside the dependency and the applications that use it.
Check dependencies against your license policy.
Define which licenses your organization accepts, restricts, or prohibits. Apply those rules to direct and transitive dependencies to identify packages that need review.
License Compliance
87%
compliant
Total libraries
312
Compliant
271
Non-compliant
3
Unknown license
14
Resolve ambiguous license information.
Review multiple licenses, alternative license expressions, and differences between registry metadata and shipped files. Keep the evidence and dependency context together when making a decision.
Share the evidence for a license review.
Export a license inventory with detected licenses, supporting files, obligations, policy results, and affected applications. Give reviewers the context behind each entry.
Frequently asked questions
Yes. Organizations can classify licenses according to their own accepted, restricted, and prohibited categories and evaluate dependencies against that policy.
Yes. License findings remain connected to the complete dependency path and the application in which the component was discovered.
Review the licenses in your own dependencies.
Walk through detected licenses, supporting evidence, and policy results with our team.