licensee/licensed
Licensed
Licensed is a command-line utility for auditing open-source dependencies and validating compliance policies across multi-language packages. Written in Ruby, the tool scans project dependencies to identify external libraries, discovers associated license files and legal notices across directory hierarchies, and caches metadata directly within the repository for historical review.
The tool evaluates detected dependencies against defined compliance rules that handle accepted licenses, ignored lists, and configuration settings specified in YAML or JSON formats. It supports custom dependency source configuration and combines all discovered copyright notices and license texts into a single distribution-ready compliance document. Additionally, the utility integrates into continuous integration pipelines to execute compliance checks and provides automated configuration migration to update files and cached records for newer versions.
Features
- Open Source License Detectors - Validates project dependencies against defined compliance policies and tracks legal metadata changes in the repository.
- Cross-Language Detectors - Scans projects across multiple programming languages and package managers to identify external software dependencies.
- Compliance Rules - Evaluates detected dependencies against defined compliance rules that handle accepted licenses and ignored lists.
- Distribution Compliance Document Generators - Aggregates all dependency copyright notices and license texts into a single compliance file ready for software distribution.
- Notice Archives - Combines discovered dependency copyright notices and license texts into a single distribution-ready compliance document.
- Inventory Extractions - Scans project directories and package managers to discover external libraries requiring verification.
- Repository Caches - Saves legal text and license metadata directly into the repository for historical auditing and review.
- Compliance Verification Pipelines - Executes compliance checks automatically within continuous integration pipelines on hosting platforms.
- Multi-Language Scanners - Scans project dependencies across various package managers and languages to verify license information.
- Status Validators - Validates that every detected dependency has up-to-date metadata, an approved license, or is explicitly ignored.
- Build Verifications - Caches and checks dependency license status against defined compliance rules during builds or checks.
- File Path Discoveries - Searches directory hierarchies and parent paths to discover license files and legal notices associated with dependencies.
- Notice Generators - Aggregates all dependency copyright notices and license texts into a single compliance file for distribution.
- Ruby License Scanners - Provides a Ruby gem that caches and verifies dependency licenses, aggregates copyright notices, and runs compliance checks in CI pipelines.
- Dependency License Aggregation - Scans software dependencies across various package managers to verify and cache their license status against approved policies.
- Hierarchical Discoveries - Traverses directory trees and parent paths to locate legal notices and license files associated with specific dependencies.
- Legal Metadata Stores - Stores legal texts and license records directly inside version-controlled repository directories to enable historical auditing.
- Multi-Ecosystem Scanners - Scans project directories across diverse ecosystems by delegating discovery to specialized language-specific source adapters.
- Custom Source Adapters - Enables implementing custom enumerators with environment checks to support additional package managers.
- Multi-Package Legal Notice Scanners - Detects project dependencies across multiple package managers and locates associated legal notices and license files.
- Repository-Cached Compliance Audits - Saves legal text and license metadata for project dependencies directly into the repository for review and historical auditing.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
