licensee/licensed
59.1
Adequate · 6 November 2026
4.6k
lines of production code
Ruby
primary language
4
measurements over time
What this system is
This system is a command-line tool for detecting and reporting software licenses across a wide variety of package managers and ecosystems. It enumerates dependencies from sources such as Bundler, NPM, Cargo, Gradle, and CocoaPods to identify their licensing terms. The tool provides commands to cache license data, check compliance status, list dependencies, and generate third-party notice files. It supports structured output formats and includes migration utilities for upgrading between major versions.
How it got here
2018 — v5 architecture and workflow overhaul
17 changes.
The project underwent a major v5 release, introducing a modular command architecture, a new DependencyRecord model, and expanded support for numerous package managers. This period also saw a significant infrastructure shift, migrating CI to GitHub Actions, updating the Ruby target, and replacing legacy source implementations with a consolidated sources module.
2019 — CLI architecture and reporting overhaul
11 changes.
The project refactored its core CLI structure by introducing a modular command hierarchy and a new base Reporter class to support diverse output formats like JSON, YAML, and notices. This architectural shift was accompanied by a migration to a v2 cache format and the addition of configurable content versioning strategies for source helpers. Comprehensive test suites were developed to validate the new command execution flows, reporter implementations, and migration logic.
2020–2023 — multi-language source support and testing
11 changes.
This period focused on expanding dependency source support for modern package managers, notably adding Yarn Berry (v2+) and adapting to Bundler 2.4.1+ changes. It also significantly broadened test coverage by introducing fixtures and validation logic for diverse ecosystems including NuGet, Swift, Rust/Cargo, Go dep, CocoaPods, and multi-project Gradle builds.
Features
Add support for Yarn Berry (v2+) dependency enumeration
The tool now supports enumerating dependencies for Yarn Berry (version 2.0 and above) via a new \Yarn::Berry\ source class, which uses \yarn info\ to resolve package metadata. This complements the existing \Yarn::V1\ source (for versions \< 2.0) that uses \yarn list\ and \yarn licenses list\. The new source ensures that projects using modern Yarn versions are correctly identified and their dependencies enumerated without crashing or falling back to unsupported methods.
lib/licensed/sources/yarn · high confidence
Added configurable content versioning strategy
The source helper now supports a configurable version strategy, allowing users to choose between identifying content via Git commit history or by hashing file contents. This new \ContentVersioning\ module introduces a \contents\_version\ method that respects a \version\_strategy\ configuration option (defaulting to Git for backward compatibility), enabling more stable or deterministic version detection based on actual file data rather than repository state.
lib/licensed/sources/helpers · high confidence
Expanded package manager support with new and refactored license sources
The \lib/licensed/sources\ directory now includes dedicated source implementations for a wider range of package managers, enabling license detection for Rust (Cargo), PHP (Composer), Elixir (Mix), Go (via both \dep\ and Go modules), Java/Kotlin (Gradle), iOS (CocoaPods), and Git submodules. Existing sources for Bundler, NPM, and NuGet have been significantly refactored to improve robustness, such as NPM's handling of npm 7+ peer dependencies and NuGet's extraction of license metadata from \.nuspec\ files. This change allows the tool to automatically discover and report licenses for dependencies across these additional ecosystems.
lib/licensed/sources · high confidence
New reporters for structured output and notices generation
The \lib/licensed/reporters\ directory now includes new reporter implementations that expand how command results are presented and consumed. Users can now generate machine-readable reports in JSON or YAML formats via \JsonReporter\ and \YamlReporter\ (with YAML output sanitized to remove nil values). Additionally, a \NoticesReporter\ has been added to automatically write third-party licensing notices to a file, while \CacheReporter\ and \StatusReporter\ provide detailed shell output for dependency caching and status checking, including specific warnings and error reporting for individual dependencies.
lib/licensed/reporters · high confidence
New source-setup scripts for multiple package managers
Added executable setup scripts in script/source-setup for bower, bundler, cabal, cargo, cocoapods, composer, dep, git\_submodule, go, mix, npm, nuget, pip, pipenv, pnpm, and swift. Each script prepares the corresponding test fixtures by installing dependencies (e.g., npm install, pip install, swift package resolve) and supports a -f flag to force a clean setup, ensuring consistent test environments across different language ecosystems.
script/source-setup · high confidence
Removals
Removal of legacy cache, list, and status command implementations
The legacy Ruby implementations for the cache, list, and status commands have been removed from the codebase. This deletion eliminates the previous logic for caching license text in .txt files, listing dependencies, and checking license status (including validation of cached versions and allowed/reviewed states). Users relying on these specific command behaviors should note that the underlying command structure has been replaced.
lib/licensed/command · high confidence
Removal of legacy source implementations
The legacy source implementations for Bundler, Go, NPM, and Manifest have been removed from the codebase. This change eliminates the direct handling of these dependency types within this location, indicating that their functionality has been migrated to other parts of the system or replaced by new approaches.
lib/licensed/source · high confidence
Behavioural changes
Add separate setup scripts for Yarn v1 and Yarn Berry
New executable scripts have been added at script/source-setup/yarn/v1 and script/source-setup/yarn/berry to handle source setup for their respective Yarn versions. Each script verifies that a local Yarn installation is available, navigates to the corresponding test fixtures directory (test/fixtures/yarn/v1 or test/fixtures/yarn/berry), and runs yarn install, supporting a -f flag to force a clean before installation.
script/source-setup/yarn · high confidence
Improved Bundler compatibility and reporting structure
The licensed tool now handles missing gem specifications more gracefully by introducing a MissingSpecification class that prevents enumeration from halting when a gem cannot be found, instead returning a placeholder object. This change also includes a compatibility fix for Bundler 4.x by conditionally prepending the lazy specification handler only for versions prior to 4.0.0. Additionally, the reporting system has been restructured with a new base Reporter class that defines begin/end hooks for commands, apps, sources, and dependencies, providing a cleaner foundation for future reporting features.
licensed · high confidence
Introduces dedicated scripts for setup, testing, and gem management
The project now provides a set of executable scripts in the \script/\ directory to streamline development and CI workflows. \script/setup\ and \script/test\ offer standardized entry points for running the Rake setup task and executing tests (supporting both full suites and specific files), while \script/bump-production-gems\ allows for conservative updates of specific production dependencies. Additionally, \script/verify-gem-version\ ensures consistency between source code, git tags, and built gem metadata, and \script/development-env\ loads local environment configurations. The existing \script/bootstrap\ and \script/cibuild\ scripts have been refactored to use these new utilities and modernize their dependency installation logic.
script · high confidence
Major library restructuring and removal of GitHub license fetching
The core library has been significantly refactored to support a v2 architecture. The most notable behavioral change for users is the removal of automatic license fetching from GitHub; the code previously using the Octokit gem to retrieve license content from GitHub URLs has been deleted, meaning the tool no longer fetches license data from GitHub repositories directly. Additionally, the internal module structure has been reorganized: individual source loaders (such as Bundler, Bower, NPM, etc.) are now consolidated into a single 'sources' module, the 'License' class has been renamed to 'DependencyRecord', and new infrastructure for commands, reporters, and migrations has been introduced.
lib · high confidence
Major version 5.0 release with new command structure and dependency model
Licensed has been upgraded to version 5.0, introducing a new modular command architecture where CLI commands (cache, status, list, notices, env) are now distinct classes rather than methods within the CLI. The dependency model has shifted from inheriting from a custom License class to using Licensee's FSProject, enabling more robust license detection and the ability to track multiple license files per dependency. A new \DependencyRecord\ class handles caching and comparison of license data, replacing the previous YAML frontmatter format with a structured \.dep.yml\ format. The CLI now supports a \--sources\ flag to evaluate specific package managers, a \--format\ flag for JSON/YAML output, and a \--data-source\ flag for the status command to check compliance against configuration or cached records. Additionally, a new \migrate\ command is available to assist with upgrading from previous major versions.
lib/licensed · high confidence
Major workflow overhaul: migration to GitHub Actions, Ruby 4.0.4, and new setup/test tasks
This release introduces significant changes to the development and release workflow. The CI system has migrated from Travis CI to GitHub Actions, and the project now targets Ruby 4.0.4 (up from 2.4.0). The \CHANGELOG.md\ is replaced by a link to GitHub releases. For contributors, the setup process now requires running \bundle exec rake setup\ to prepare test fixtures before running \bundle exec rake test\. A new \script/setup\ command automates source toolchain installation, and a \.licensed-dev-env\ file allows persistent local tool configuration. The release process is now driven by Git tags rather than manual version bumps in code, and the gem is published automatically via GitHub Actions upon creating a release. Additionally, RuboCop linting is integrated into the default rake task, and configuration files (\.licensed.yml\, \.licensed.test.yml\) are explicitly defined for license checking.
(repo-wide) · high confidence
Migration to v2 cache format and bundler source naming
The v2 migration updates cached records to reflect the bundler source type change from 'rubygem' to 'bundler'. This involves renaming the 'rubygem' configuration key to 'bundler' in the config file, moving cached data from the 'rubygem' folder to 'bundler', and converting individual cached records from .txt files with YAML frontmatter to .dep.yml files. The new format stores license and notice text as structured YAML properties rather than plain text separated by dividers.
lib/licensed/migrations · high confidence
Refactored commands into a modular class hierarchy with new environment and notices commands
The command implementation has been restructured around a new base \Command\ class, allowing individual commands like \Cache\, \Status\, \List\, \Notices\, and the new \Environment\ command to inherit shared execution logic. This change introduces a new \Environment\ command that outputs application configuration details (such as source paths, cache paths, and enabled sources) in YAML format, and a \Notices\ command that generates notice files from either live dependency data or cached records. The \Status\ command now supports a \data\_source\ option to check compliance against either configuration entries or cached metadata, and the \Cache\ command includes logic to clean up stale cached records that no longer match current dependencies.
lib/licensed/commands · high confidence
Support for Bundler 2.4.1+ local search behavior
The Bundler source adapter now includes a new definition extension that overrides the \specs\ and \bundler\_query\ methods to ensure compatibility with Bundler 2.4.1 and higher. This change adapts to internal implementation changes in newer Bundler versions, specifically handling how the \bundler\ gem itself is resolved and preventing \Gem::NotFound\ errors during license detection.
lib/licensed/sources/bundler · high confidence
Test coverage
Added Cabal test fixtures; Added CocoaPods test fixture; Added NuGet test fixture with source configuration; Added Rust/Cargo test fixture; Added Swift test fixtures and initial SPM support; Added test coverage for command execution, caching, listing, status, and notices; Added test coverage for dependency source implementations; Added test coverage for the reporter subsystem; Added test fixtures and configuration for bundler tests; Added test fixtures for Go dep dependency management; Added test fixtures for Gradle multi-project builds; Added test fixtures for Mix-based Elixir projects; Added test fixtures for Yarn Berry (v3.1.1); Added test fixtures for license manifest validation; Added test helpers for command, reporter, shell, and source testing; Added tests for V2 migration logic; Added tests for Yarn v1 and Berry source parsers; Added tests for the ContentVersioning helper; Expanded test coverage for core classes and development scripts; Removed legacy command tests; Removed test suite for source detection modules; Updated Go test fixture to include vendored dependencies and module structure.
Dependencies
Update Ruby dependencies and add test fixtures for supported package managers
The project's Ruby dependencies have been updated, including upgrading to Licensee 10.0.0 and adding the \csv\ gem for Ruby 3.4+ compatibility. To support testing these changes and new ecosystem integrations, test fixtures have been added for Cargo (Rust), CocoaPods, Composer (PHP), Go modules, Gradle (multi-project), Mix (Elixir), npm (with workspaces), NuGet, pip, pipenv, and pnpm.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 51 → 59 (+8.6)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 98 → 98 (+0.0)
- Architecture 54 → 54 (+0.0)
- Maturity 32 → 53 (+21.3)
- Readiness 82 → 82 (-0.1)
- Security 73 → 63 (-10.7)
Resolved (4)
- Ambiguous overlap between enumerate_dependencies and dependencies in the Source base class. enumerate_dependencies is implemented by all specific sources, but dependencies is also present on the base class. It is unclear if dependencies() is a cached wrapper, a different implementation, or a legacy alias. This creates confusion for consumers regarding which method to call for the actual list of dependencies.
- Coverage not measured — no coverage collector is wired up
- Inconsistent naming convention for CLI entry points. Most methods use simple imperative verbs (cache, status, list, notices, migrate), but CLI.exit_on_failure?() uses a predicate suffix (?) which is inconsistent with the other action-oriented methods and suggests a configuration check rather than a command execution.
- Redundant reporter creation methods on Command. Both create_reporter and default_reporter exist on the same class with similar signatures. It is unclear why a caller would choose one over the other, or if they serve distinct purposes (e.g., one for custom vs. default). This duplicates intent.
New (1)
- Outdated: csv
Architecture
- Unchanged — 0 containers · 1 contexts · 0 edges
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
licensee/licensed was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 6 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit f5357d777e4df1e1ffb8bd83a55db7071136d6de — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-60d1b390edf0.