License compliance across the complete dependency graph.
Farion analyzes the license files that ship with direct and transitive dependencies, connects them to the affected applications, and evaluates the resulting obligations against your policies.
Base license decisions on the dependency contents.
Registry metadata can be incomplete, outdated, or ambiguous. Farion inspects the license files and package contents associated with a dependency and preserves the evidence behind the detected result.
Understand what each license requires.
Review attribution, notice, source-disclosure, redistribution, modification, and other obligations in the context of the dependency and the applications that use it.
Apply your own license rules consistently.
Define accepted, restricted, or prohibited licenses and evaluate every direct and transitive dependency against the configured policy.
License Compliance
87%
compliant
Total libraries
312
Compliant
271
Non-compliant
3
Unknown license
14
node-forge@1.3.1iText@7.2.5qrcode-generator@1.4.4Handle multiple licenses and conflicting evidence.
Farion retains alternative license expressions, multiple shipped license files, conflicts between metadata and package contents, and the dependency context required for a review.
Export a reviewable license inventory.
Generate license reports with the dependency path, detected licenses, supporting files, obligations, policy result, and affected application. Enterprise customers can create custom reports through the API and reporting integrations.
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.
See how Farion works on your application.
Request a guided evaluation or walk through the relevant workflow with our technical team.