SlatherOrg/slather
61.5
Adequate · 6 November 2026
2.3k
lines of production code
Ruby
primary language
4
measurements over time
What this system is
Slather is a command-line tool that generates code coverage reports for Xcode projects by parsing gcov and LLVM profdata outputs. It supports multiple output formats, including HTML, JSON, Cobertura XML, and SonarQube XML, and integrates with various CI/CD platforms. The tool also provides a CocoaPods plugin to automate project setup for coverage generation.
How it got here
2014 — Initial project scaffolding and coverage engine development
15 changes.
This period established the foundational structure of the Slather project, including repository initialization, CI configuration, and the core CLI interface. It focused on implementing the primary code coverage parsing engine, specifically adding support for modern Xcode profdata formats alongside existing gcov support. The work also expanded reporting capabilities to include multiple output formats and integrated with various CI/CD platforms.
2015–2021 — CLI modularization and HTML report enhancements
5 changes.
The project refactored its command-line interface into modular subcommands, expanding support for multiple CI/CD platforms and diverse output formats like SonarQube and LLVM-cov. Concurrently, HTML coverage reports were significantly enhanced with syntax highlighting, client-side list management, and improved styling. The test suite was also expanded to validate these new features, including specific fixtures for Xcode workspace scheme handling and Unicode character support.
Features
Added syntax highlighting and list management assets for HTML reports
The HTML output now includes syntax highlighting for source code and enhanced list management for file listings. This is achieved by adding \highlight.pack.js\ (highlight.js) to colorize code blocks, \list.min.js\ (List.js) to handle client-side sorting, filtering, and pagination of the file index, and \slather.css\ to style the coverage reports and integrate the highlight.js theme.
assets · high confidence
Initial project scaffolding and CI configuration
The repository is initialized with core project files including a MIT license, a comprehensive changelog, and detailed usage documentation. Continuous integration is configured for Travis CI using Xcode 12.2 and Bundler 2.0, with a \.coveralls.yml\ file set up to report coverage to Travis CI. A \.gitignore\ file is added to exclude build artifacts, IDE settings, and coverage reports, while a Rakefile provides tasks for running specs.
(repo-wide) · high confidence
Introduce slather CLI entry point with setup, coverage, and version commands
The bin/slather executable is added as the primary command-line interface for the tool. It uses the Clamp library to define three subcommands: 'setup' for configuring an Xcode project for test coverage generation, 'coverage' for computing coverage reports, and 'version' for printing the current slather version. The 'coverage' subcommand is set as the default when no subcommand is specified.
bin · high confidence
Introduction of CocoaPods plugin and coverage output services
Slather now includes a CocoaPods plugin that automatically configures projects for coverage during the post-install phase, replacing the deprecated \prepare\_pods\ method. The library also expands its reporting capabilities by introducing new coverage services for Cobertura XML, Hardcover, Gutter JSON, Simple JSON, HTML, JSON, LLVM-cov, and SonarQube XML outputs.
lib · high confidence
New coverage output formats and CI integrations
Slather now supports generating coverage reports in Cobertura XML, SonarQube XML, Gutter JSON, and simple JSON formats, alongside an LLVM-cov compatible output. The HTML report has been enhanced to display branch coverage statistics and line counts. Additionally, the tool now integrates with multiple CI/CD platforms including GitHub Actions, CircleCI, Buildkite, Bitrise, and Jenkins, automatically detecting build metadata and job IDs for these services.
_lib/slather/coverage\service · high confidence
Slather v2.8.5: New profdata coverage engine and project setup automation
Slather has been updated to version 2.8.5, introducing a new \ProfdataCoverageFile\ class that parses \llvm-cov\ profdata output to support modern Xcode code coverage formats alongside the existing gcov support. The \Project\ class now includes a \slather\_setup\_for\_coverage\ method (aliased as \setup\_for\_coverage\) that automatically configures Xcode schemes and build settings for either gcov or clang coverage. Additionally, the \CoverageInfo\ module provides standardized metrics for line and branch coverage, while \CoverallsCoverage\ adds JSON serialization for Coveralls integration.
lib/slather · high confidence
Behavioural changes
Refactored CLI into modular subcommands with expanded configuration and output options
The command-line interface has been restructured into distinct subcommands (coverage, setup, and version) to improve organization and maintainability. This change introduces several new capabilities for users: support for multiple CI/CD platforms including GitHub Actions, TeamCity, and Buildkite; new output formats such as SonarQube XML, LLVM-cov, and simple JSON; and enhanced configuration flexibility via the \--ymlfile\ option to specify custom configuration files, \--workspace\ for Xcode workspaces, \--arch\ for universal binaries, and \--source-files\ for filtering source code. Additionally, HTML output now supports CDN-hosted assets and configurable decimal precision.
lib/slather/command · high confidence
Test coverage
Added HTML coverage fixtures for test validation; Added Xcode fixture files for branch coverage and empty source testing; Added Xcode project fixture schemes for multi-target and dynamic library testing; Added test coverage for CocoaPods plugin integration and coverage file parsing; Added test coverage for new and existing coverage service outputs; Added test fixture for Xcode workspace scheme handling; Added test fixtures for Objective-C, C++, and Swift source files; Added test fixtures for branch coverage, multi-target schemes, and Unicode filenames; Added test fixtures for new coverage output formats and multi-binary scenarios; Added tests for the FixtureFramework; Expanded test fixture project with multi-language and multi-target support; Test infrastructure setup for Xcode workspace and coverage fixtures.
Dependencies
Initial gemspec and Gemfile setup for Slather
The project introduces its primary dependency manifest files: a \Gemfile\ that delegates to the gemspec, and a \slather.gemspec\ defining the library's runtime and development dependencies. Runtime dependencies include \clamp\ (\~\> 1.3), \xcodeproj\ (\~\> 1.27), \nokogiri\ (\>= 1.14.3), \CFPropertyList\ (\>= 2.2, \< 4), and \activesupport\. Development dependencies are pinned to specific versions for \bundler\ (\~\> 2.0), \coveralls\ (\~\> 0.8), \simplecov\ (\~\> 0), \rake\ (\~\> 12.3), \rspec\ (\~\> 3.8), \pry\ (\~\> 0.12), \cocoapods\ (\~\> 1.10.beta.1), \json\_spec\ (\~\> 1.1), and \equivalent-xml\ (\~\> 0.6).
(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 60 → 61 (+1.2)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 73 → 73 (+0.0)
- Architecture 91 → 91 (+0.0)
- Maturity 52 → 54 (+2.8)
- Readiness 56 → 56 (+0.1)
- Security 86 → 84 (-1.7)
Resolved (5)
- Duplicate intent across similar types. Slather.CoverageFile and Slather.ProfdataCoverageFile share identical method signatures for line_coverage_data and branch_coverage_data. While they may handle different underlying formats (gcov vs profdata), the public API surface exposes redundant method names for the same logical operation (getting line/branch coverage). Additionally, ProfdataCoverageFile has branch_region_data which has no counterpart in CoverageFile, creating an asymmetry.
- Inconsistent method naming for report generation. CoberturaXmlOutput and SonarqubeXmlOutput use create_xml_report, while HtmlOutput uses create_html_reports (plural) and create_html_from_file (singular). The naming convention varies between 'create_[format]report' and 'create[format]s'.
- Inconsistent method naming for storing reports. Some output types use store_report, while others (like HtmlOutput) do not have this method, instead using create_html_reports. This suggests store_report is for saving to disk/cloud, while create_* is for generation. However, the lack of store_report in HtmlOutput and SimpleOutput makes the API inconsistent for the 'save' operation.
- Inconsistent naming convention for data retrieval methods. Some methods return a path (pathname), some return raw content (data), and some return processed coverage metrics. However, source_file() vs source_file_pathname() is ambiguous: does one return the string path and the other the file object? Similarly, raw_data() vs source_data() vs gcov_data() suggests overlapping or unclear distinctions between raw file content, parsed GCov format, and internal raw representation.
- Outdated: activesupport
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
SlatherOrg/slather 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 ef903ce54346e8abd4607297193fc42d572f50d8 — 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.2+preprod-5c4e66d9318b.