Score Tooling

A unified Bazel module containing development tools and utilities for building, testing, and maintaining code quality.

Quick Start

Add this module to your MODULE.bazel:

bazel_dep(name = "score_tooling", version = "1.0.0")

Available Tools

Each tool maintains its own documentation and examples in their respective subdirectories. See the individual README files for detailed usage instructions and configuration options.

Tool	Description	Documentation
cli_helper	Command-line interface utilities	README
cr_checker	Code review and compliance checking	README
dash	Eclipse Dash license scanning	README
format	Code formatting validation	README
lint	Python lint aspects (ruff, pylint)	README
python_basics	Python development utilities and testing	README
starpls	Starlark language server support	README
tools	Formatters & Linters	README
coverage	Unified LLVM source-based coverage (C++ + Rust)	README

Coverage

The coverage/ module provides the reusable LLVM source-based coverage pipeline used across S-CORE repositories: one report covering C++ and Rust (line + branch), exact 0% entries for untested in-scope files, a justification system (COV_JUSTIFIED markers + YAML), and effective-coverage gating. See the adoption guide and the mechanism deep-dive.

Breaking change: the former Ferrocene symbol-report/blanket workflow (rust_coverage_report, //coverage:ferrocene_report) was removed. The LLVM pipeline replaces it with unified C++ + Rust reports; see the adoption guide for migration.

Generate a combined Rust + Python HTML coverage report for this repository's own tools (plantuml, validation, manual_analysis):

bazel run //coverage:combined_report

Usage Examples

Load tools in your BUILD files:

load("@score_tooling//:defs.bzl", "score_py_pytest")
load("@score_tooling//:defs.bzl", "cli_tool")
load("@score_tooling//coverage:defs.bzl", "score_coverage_reporter", "score_coverage_scope")

Declare the coverage scope and reporter for your repository (see the coverage adoption guide for the full setup, including the required .bazelrc configuration and toolchains):

score_coverage_scope(
    name = "coverage_scope",
    testonly = True,
    deps = ["//src/mylib"],
)

score_coverage_reporter(
    name = "reporter_wrapper",
    testonly = True,
    coverage_scope = ":coverage_scope",
    llvm_cov = "@llvm_toolchain//:llvm-cov",
    llvm_profdata = "@llvm_toolchain//:llvm-profdata",
    llvm_cxxfilt = "@llvm_toolchain_llvm//:bin/llvm-cxxfilt",
)

Upgrading from separate MODULES

If you are still using separate module imports and want to upgrade to the new version. Here are two examples to showcase how to do this.

load("@score_python_basics//:defs.bzl", "score_py_pytest") => load("@score_tooling//:defs.bzl", "score_py_pytest")
load("@score_cr_checker//:cr_checker.bzl", "copyright_checker") => load("@score_tooling//cr_checker:cr_checker.bzl", "copyright_checker")

All things inside of 'tooling' can now be imported from @score_tooling//:defs.bzl. The available import targets are:

• score_virtualenv
• score_py_pytest
• dash_license_checker
• cli_helper
• setup_starpls
• score_coverage_scope
• score_coverage_reporter

Formatting, linting, and cr_checker are no longer re-exported from defs.bzl; use @score_tooling//third_party/format:macros.bzl, @score_tooling//third_party/lint:macros.bzl, @score_tooling//cr_checker:cr_checker.bzl, or the @score_tooling//third_party/format:rustfmt_with_policies label directly.

Format the tooling repository

bazel run //:format.fix