Integration Dashboard

Snapshot: 2026-08-28T09:19:12Z

🔒 Add a GitHub personal access token (PAT) for live status — exact commit counts fetched directly from GitHub. Enter it in the token field above, or create one here. Without a token, up-to-date / behind status is still shown from data embedded at report generation time. Your PAT is not sent anywhere — it is only kept in the local cache of this page.

Traceability Overview

This tab provides an overview of requirements, architecture, and test traceability for the S-CORE reference integration. Detailed models are maintained in Sphinx with sphinx-needs and linked below.

Requirements & Architecture

Central documentation and needs-based traceability are published via Sphinx. Use the links below to inspect coverage between requirements, design, tests, and components.

ISO 26262 Alignment

For ISO 26262, this view will be extended to expose:

  • Traceability from system requirements → software components → tests.
  • Links to Safety Sentinel–based checks in the Bazel build.
  • Automated coverage metrics derived from Sphinx-Needs exports (future).

SBOM & Tool Qualification

Product SBOM (ISO 26262) and tool qualification overview for the S-CORE reference integration.

Product SBOM

Package Version Supplier Licenses

Tool Qualification (ISO 26262)

Tools used in the build, analysis, and verification pipeline are documented separately and linked here. Detailed qualification information is maintained in the S-CORE tooling documentation.

Static Analysis & Code Quality

SBOM & Dependency Tools

SBOM generation and dependency analysis tools (e.g., Syft, Grype) are configured in CI and documented as part of the tooling landscape. A dedicated tool-qualification table will be added here once a central manifest is available.