Overall Status#
Important
Data collected on: 2026-09-04
Note
This status overview is generated with AI assistance and is not yet fully accurate. It is intended as a directional snapshot — the trend and structure are correct, but individual figures and statuses may still be off. Treat the numbers as indicative until the underlying data sources are fully validated.
This page tracks feature and process status across the SCORE platform modules.
It is regenerated from live eclipse-score GitHub repositories pinned via
known_good.json.
Changes in this snapshot
The progress charts now carry a fifth column, v0.9 — this snapshot is measured against the
release_candidate_09pins, so the v0.8 column holds the previously published release figures.Kyron is tracked as a module for the first time (12 module rows instead of 11). It ships code, unit tests, Rust coverage, a Clippy gate and a large component-integration suite, but has no requirements, architecture or detailed-design documents yet.
The
scorerepository was restructured: component documentation moved fromdocs/modules/<module>/into the individual module repositories, anddocs/features/analysis-infra/loggingbecamedocs/features/log_and_trace/logging. All path filters were rebuilt against the pinned trees.Several modules migrated their requirements to TRLC (Communication, Config Management). Where an RST set and a TRLC set describe the same feature area, only the larger of the two is counted — the duplicate is suppressed to avoid double counting.
Time and Config Management are now pinned in
known_good.json, so their source links point at a fixed commit instead ofmain.Security/Crypto and Some/IP are not pinned in
known_good.jsonand therefore no longer part of the reference integration CI. Their unit-test and coverage cells are marked 🔄 Module CI only and link to the workflows in their own repositories.The PA2 feature-requirement total decreased (341 → 297) because the Lifecycle feature requirements were consolidated during the restructuring (92 → 32); the component-requirement total grew strongly (607 → 783).
Process Area 1 — Change Management#
Process Status
Process req. status |
ISO 26262 std_req status |
Req. verification status |
|---|---|---|
Module |
CR approved |
|---|---|
Baselibs |
✅ Accepted |
Communication |
✅ Accepted
|
Logging |
✅ Accepted
|
Persistency |
✅ Accepted
|
Time |
✅ Accepted
|
Config Mgmt |
✅ Accepted
|
Lifecycle |
✅ Accepted
|
Kyron |
🔄 In Progress |
Security/Crypto |
✅ Accepted
|
Diagnostic Services |
✅ Accepted
|
NM |
❌ Open |
Some/IP |
✅ Accepted
|
Process Area 2 — Requirements Engineering#
Process Status
Process req. status |
ISO 26262 std_req status |
Req. verification status |
|---|---|---|
Fig. 1 Total Feature and Component Requirements across the 12 tracked modules per release (v0.5.0-beta → v0.6.0 → v0.7.0 → v0.8 → v0.9).#
Module |
Feature Req |
Component Req |
Req. Inspection |
|---|---|---|---|
Baselibs |
✅ Available (14/14)
|
✅ Available (136/136 comp_req + 32/32 AoU)
|
🔄 40% (4/10) |
Communication |
✅ Available (64/64) |
✅ Available (363/363 comp_req + 38/38 AoU)
|
❌ Open |
Logging |
✅ Available (46/46)
|
✅ Available (39/39 comp_req + 5/5 AoU) |
🔄 0% (0/3) |
Persistency |
✅ Available (37/37)
|
✅ Available (35/35 comp_req)
|
✅ Available (2/2)
|
Time |
✅ Available (15/15)
|
🔄 0% (0/4 AoU)
|
🔄 0% (0/4) |
Config Mgmt |
✅ Available (20/20)
|
✅ Available (47/47 comp_req + 1/1 AoU) |
❌ Open |
Lifecycle |
✅ Available (32/32)
|
✅ Available (64/64 comp_req + 1/1 AoU)
|
🔄 0% (0/2) |
Kyron |
❌ Open |
❌ Open |
❌ Open |
Security/Crypto |
✅ Available (41/41)
|
🔄 70% (1/1 comp_req + 6/9 AoU) |
🔄 0% (0/2)
|
Diagnostic Services |
✅ Available (22/22)
|
❌ Open |
❌ Open |
NM |
❌ Open |
❌ Open |
❌ Open |
Some/IP |
✅ Available (6/6)
|
✅ Available (8/8 comp_req)
|
❌ Open |
Process Area 3 — Architecture Design#
Process Status
Process req. status |
ISO 26262 std_req status |
Req. verification status |
|---|---|---|
Fig. 2 Total Feature and Component Architecture elements across the 12 tracked modules per release (v0.5.0-beta → v0.6.0 → v0.7.0 → v0.8 → v0.9).#
Module |
Feature Arch |
Component Arch |
Arch. Inspection |
|---|---|---|---|
Baselibs |
✅ Available (3/3) |
🔄 99% (197/198)
|
🔄 80% (8/10) |
Communication |
✅ Available (3/3)
|
✅ Available (17/17)
|
❌ Open |
Logging |
✅ Available (2/2) |
✅ Available (13/13) |
🔄 0% (0/2) |
Persistency |
✅ Available (9/9)
|
🔄 40% (2/5) |
🔄 0% (0/2)
|
Time |
✅ Available (1/1)
|
✅ Available (2/2) |
❌ Open |
Config Mgmt |
✅ Available (1/1)
|
❌ Open |
❌ Open |
Lifecycle |
✅ Available (7/7) |
✅ Available (45/45) |
🔄 0% (0/3) |
Kyron |
❌ Open |
❌ Open |
❌ Open |
Security/Crypto |
✅ Available (1/1)
|
🔄 16% (4/25)
|
🔄 0% (0/3) |
Diagnostic Services |
✅ Available (1/1)
|
❌ Open |
❌ Open |
NM |
❌ Open |
❌ Open |
❌ Open |
Some/IP |
✅ Available (1/1) |
✅ Available (4/4) |
❌ Open |
Process Area 4 — Implementation#
Process Status
Process req. status |
ISO 26262 std_req status |
Req. verification status |
|---|---|---|
Fig. 3 Estimated Lines of Code across the 12 tracked modules per release (v0.5.0-beta → v0.6.0 → v0.7.0 → v0.8 → v0.9).#
Module |
SW Dev Plan |
Code |
Detailed Design |
Impl. Inspection |
|---|---|---|---|---|
Baselibs |
✅ Available |
✅ Available (~322,600 LOC)
|
🔄 Draft (1 design doc(s), 0 |
🔄 0% (0/9) |
Communication |
✅ Available |
✅ Available (~363,000 LOC)
|
🔄 Draft (1 design doc(s), 0 |
❌ Open |
Logging |
✅ Available |
✅ Available (~79,700 LOC)
|
🔄 Draft (2 design doc(s), 0 |
🔄 0% (0/2) |
Persistency |
✅ Available |
✅ Available (~18,000 LOC)
|
🔄 Draft (1 design doc(s), 0 |
🔄 0% (0/1)
|
Time |
✅ Available |
✅ Available (~26,600 LOC)
|
🔄 Draft (4 design doc(s), 0 |
🔄 0% (0/4) |
Config Mgmt |
✅ Available |
✅ Available (~23,300 LOC)
|
❌ Open |
❌ Open |
Lifecycle |
✅ Available |
✅ Available (~68,200 LOC)
|
🔄 Draft (2 design doc(s), 0 |
🔄 0% (0/2) |
Kyron |
✅ Available |
✅ Available (~38,600 LOC)
|
❌ Open |
❌ Open |
Security/Crypto |
✅ Available |
✅ Available (~82,700 LOC)
|
🔄 Draft (2 design doc(s), 0 |
🔄 0% (0/2)
|
Diagnostic Services |
✅ Available |
❌ Open |
❌ Open |
❌ Open |
NM |
✅ Available |
❌ Open |
❌ Open |
❌ Open |
Some/IP |
✅ Available |
✅ Available (~37,300 LOC)
|
❌ Open |
❌ Open |
Process Area 5 — Verification#
Process Status
Process req. status |
ISO 26262 std_req status |
Req. verification status |
|---|---|---|
Fig. 4 Test counts and coverage across the 12 tracked modules per release (v0.5.0-beta → v0.6.0 → v0.7.0 → v0.8 → v0.9).#
Note
C0/C1 Coverage data is sourced from the reference_integration
CI (Code Quality & Documentation workflow,
bazel coverage --config=ferrocene-coverage). C0 = line coverage,
C1 = branch coverage. Rust coverage reports line coverage only.
Modules that are not pinned in known_good.json and therefore not
built by the reference_integration CI (Security/Crypto, Some/IP)
are marked 🔄 Module CI only and link to their own repository
workflows instead.
Note
Static Code Analysis is tracked per module via dedicated CI
workflows (clang-tidy for C++, Rust Clippy for Rust). All listed
workflows are zero-tolerance (CI fails on any finding), so a passing
main branch implies 0 open findings. Additionally, CodeQL
runs centrally across all pinned repositories in
reference_integration (finding counts require the GitHub Security
tab).
Dynamic Code Analysis is tracked via sanitizer CI workflows
(ASan/UBSan/LSan via --config=asan_ubsan_lsan, TSan via
--config=tsan). All listed workflows are zero-tolerance, so a
passing main branch implies 0 sanitizer findings.
Note
Module Verification Report additionally lists generated
traceability evidence where a module produces it. Communication builds
a L.O.B.S.T.E.R. Traceability Report (LOBSTER 1.0.6, pulled by
third_party/lobster/lobster.bzl) from the dependable_element
Bazel rule in eclipse-score/tooling. The report is assembled during
bazel build //docs/sphinx:sphinx_doc and published to GitHub Pages
by deploy_docs.yml — it is not checked into the repository, so
it does not appear in the pinned source tree. It currently covers the
message_passing dependable element only; there is no equivalent
report for LoLa / mw::com.
Module |
Unit Tests |
C0/C1 Cov |
Comp. IT |
Feat. IT |
Static |
Dynamic |
Module Ver. Rpt |
|---|---|---|---|---|---|---|---|
Baselibs |
✅ 23,976 tests
|
🔄 C0 94.9% / C1 61.7% (C++) |
✅ 6 test cases
|
❌ Open |
✅ 0 findings |
✅ ASan, LSan, UBSan |
🔄 Draft |
Communication |
✅ 3,530 tests |
🔄 C0 83.0% / C1 52.6% (C++) |
✅ 111 test cases
|
❌ Open |
✅ 0 findings |
✅ ASan, LSan, TSan, UBSan |
🔄 Draft |
Logging |
✅ 334 tests |
🔄 C0 96.6% / C1 75.4% (C++), C0 39.9% (Rust) |
✅ 8 test cases
|
✅ 2 test cases
|
✅ 0 findings |
✅ ASan, LSan, TSan, UBSan |
🔄 Draft |
Persistency |
✅ 95 tests |
🔄 C0 94.7% / C1 63.0% (C++), C0 92.7% (Rust) |
✅ 44 test cases
|
✅ 50 test cases
|
✅ 0 findings |
❌ Open |
✅ Available |
Time |
✅ 335 tests |
🔄 C0 90.3% / C1 61.4% (C++) |
✅ 7 test cases
|
❌ Open |
🔄 clang-tidy ✅, CodeQL ❌ failing |
✅ ASan, LSan, UBSan |
❌ Open |
Config Mgmt |
✅ 238 tests |
🔄 C0 92.8% / C1 64.1% (C++) |
❌ Open |
❌ Open |
✅ 0 findings |
❌ Open |
❌ Open |
Lifecycle |
✅ 478 tests
|
🔄 C0 77.4% / C1 50.7% (C++), C0 53.5% (Rust) |
✅ 58 test cases
|
❌ Open |
✅ 0 findings |
✅ ASan, LSan, TSan, UBSan |
🔄 Draft |
Kyron |
🔄 3 tests
|
🔄 C0 50.4% (Rust) |
✅ 209 test cases
|
❌ Open |
✅ 0 findings |
❌ Open |
❌ Open |
Security/Crypto |
🔄 Module CI only |
❌ Open |
✅ 10 test cases
|
❌ Open |
✅ 0 findings |
❌ Open |
🔄 Draft |
Diagnostic Services |
❌ Open |
❌ Open |
❌ Open |
❌ Open |
❌ Open |
❌ Open |
❌ Open |
NM |
❌ Open |
❌ Open |
❌ Open |
❌ Open |
❌ Open |
❌ Open |
❌ Open |
Some/IP |
🔄 Module CI only |
🔄 Module CI only |
✅ 11 test cases
|
❌ Open |
✅ 0 findings |
✅ ASan, LSan, TSan, UBSan |
❌ Open |
Platform Verification Report
Platform Verification Report — ❌ Open (single project-wide deliverable;
not yet published at the pinned score ref)