Eclipse S-CORE Verified
Eclipse S-CORE Verified provides an open, versioned suite of reproducible tests to verify that candidate distributions based on Eclipse S-CORE conform to its APIs, runtime characteristics, component integration contracts, documented external interfaces, expected behavior, and quality standards.
The Eclipse S-CORE Verified project defines “distribution” as followed: A distribution is a commercial or non commercial software stack that leverages a certain Eclipse S-CORE version as a middleware building block. The scope of the Eclipse S-CORE verified project is to:
- Define, in collaboration with the Eclipse S-CORE project and the broader Eclipse S-CORE community and the X-CORE platform council, the verification criteria that a distribution full-fills to demonstrate it is genuinely based on Eclipse S-CORE upstream components.
- Develop, maintain, and version an open verification test suite that exercises the public APIs, interfaces, runtime behaviour and integration points defined by Eclipse S-CORE.
- Provide tooling and software infrastructure that allows any party — e.g. Eclipse S-CORE contributors, distributors, OEMs, independent integrators, academia — to run the test suite themselves against a candidate distribution and obtain reproducible, comparable results.
- Define a transparent, open result-reporting format so that verification outcomes can be shared, archived, and compared across distributions and across different Eclipse S-CORE versions.
- Maintain traceability between upstream Eclipse S-CORE source artefacts (Git commits, release tags, documentation) and the corresponding versioned test assets in this project, so that verification results are unambiguously tied to a specific upstream baseline.
- Develop materials and documentation that make it straightforward for a distributor or downstream consumer to adopt the test suite and to understand the meaning — and limits — of a passing result.
- Continuously evolve the test material in sync with new S-CORE releases, newly added components, and lessons learned from real-world execution.
- The project reuses the same versioning schema and methodology of the Eclipse S-CORE project. With each Eclipse S-CORE version a corresponding version of this project shall be available.
Out of Scope
To avoid confusion with related project types and existing Eclipse S-CORE governance, the following are explicitly out of scope:
- Issuing legally binding compatibility certifications or operating a trademark licensing program. These trademark and licensing frameworks are part of a broader program developed by the Eclipse Foundation around the Eclipse S-CORE Verified project, and authority over the "Eclipse S-CORE", "S-CORE Compatible", and "S-CORE Certified" marks rests exclusively with the Eclipse Foundation.
- Determine the scope or roadmap of the Eclipse S-CORE project. This project consumes the Eclipse S-CORE specification and codebase as inputs; it does not define them.
- Functional safety assessment for a specific downstream use is out of scope.
- Eclipse Specification Project. This proposal explicitly scopes the project as a verification / test suite project. Should the S-CORE community decide in the future to pursue a formal Eclipse Specification Project with an associated Technology Compatibility Kit, the assets developed here may serve as input to such a future effort, but that transition is not part of this proposal.
Basics
- Project ID: automotive.score-verified
- PMI: https://projects.eclipse.org/projects/automotive.score-verified
- Website: https://projects.eclipse.org/projects/automotive.score-verified
- Download CSV: Commits , Issues , Reviews , IP Lab requests
Active repositories
| Repository | Commits | Reviews | Issues |
|---|
The EMO oversees the lifecycle of Eclipse projects, trademark and IP management, and provides a governance framework and recommendations on open source best practices.
See the project’s PMI page at https://projects.eclipse.org/projects/automotive.score-verified
Releases
Reviews
- Creation (2026-10-26) – see review
IP Lab requests
Organization Settings
- GitHub organization: eclipse-score-verified
- 2FA enforced:
True - Default workflow permissions:
write
Branch Protections
This project has a total of 3 repositories in its associated GitHub organization eclipse-score-verified
.
The graph below outlines the percentange of repositories that have either defined a Branch Protection Rule or Repository Ruleset: