Eclipse uProtocol
Basics
- Project ID: automotive.uprotocol
- PMI: https://projects.eclipse.org/projects/automotive.uprotocol
- Website: https://uprotocol.org
- Download CSV: Commits , Issues , Reviews , IP Lab requests
- Time range for commits: 2025-08-01 06:55:40 to 2026-08-11 06:28:48.
- Time range for issues: 2025-08-01 07:20:55 to 2026-08-10 13:37:44.
- Time range for reviews: 2025-08-01 00:29:50 to 2026-08-12 13:02:11.
Active repositories
Activity - commits
There have been 209 commits made by 9 people on 16 repositories over the last 12 months.
Activity - issues
There have been 55 issues submitted by 11 people on 15 repositories over the last 12 months.
Activity - reviews
There have been 174 reviews submitted by 14 people on 18 repositories over the last 12 months.
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.uprotocol
Releases
Reviews
- Eclipse uProtocol 2027.02 Progress (2027-02-24) – see review
- Eclipse uProtocol 2026.02 Progress (2026-02-18) – see review
- 2025.02 Progress (2025-02-19) – see review
- 2024.02 Progress (2024-02-28) – see review
- Creation (2023-04-05) – see review
IP Lab requests
- 2026-08-07 - crate/cratesio/-/http/1.5.0
- 2026-08-07 - crate/cratesio/-/uuid/1.24.0
- 2026-08-07 - crate/cratesio/-/quinn-udp/0.5.15
- 2026-08-07 - crate/cratesio/-/rustc-hash/2.1.3
- 2026-08-07 - crate/cratesio/-/chacha20/0.10.1
- 2026-08-07 - crate/cratesio/-/sha1/0.10.7
- 2026-08-07 - crate/cratesio/-/either/1.17.0
- 2026-08-07 - crate/cratesio/-/crossbeam-epoch/0.9.20
- 2026-08-07 - crate/cratesio/-/crossbeam-utils/0.8.22
- 2026-08-07 - crate/cratesio/-/thread_local/1.1.10
Organization Settings
- GitHub organization: eclipse-uprotocol
- 2FA enforced:
True - Default workflow permissions:
read
Branch Protections
This project has a total of 48 repositories in its associated GitHub organization eclipse-uprotocol
.
The graph below outlines the percentange of repositories that have either defined a Branch Protection Rule or Repository Ruleset:
SDV Maturity badges recognise achievements made by the project towards the SDV maturity assessment goals. Learn more on the dedicated page .
These badges only apply to the SDV Working Group .
Warning
This page is under construction
We are currently working on a definition and prototype for SDV badges, please see the SDV Process .
Assessing release v0.9.0 of component up-rust.
See the manifest file for this component at https://github.com/eclipse-uprotocol/up-rust/releases/download/v0.9.0/sdv-manifest.toml .
Blueprints integration
Is the project used to showcase the resolution of a real-life situation, either individually or integrated with other Eclipse SDV projects? See the SDV Blueprints project for more information.
<a href="https://github.com/eclipse-sdv-blueprints/fleet-management"><img src="https://metrics.eclipse.org/badges/automotive.uprotocol_up-rust_badge_integration.png" alt="SDV Blueprints integration badge for automotive.uprotocol - up-rust" /></a>
<a href="https://github.com/eclipse-sdv-blueprints/commercial-sdv-stack"><img src="https://metrics.eclipse.org/badges/automotive.uprotocol_up-rust_badge_integration.png" alt="SDV Blueprints integration badge for automotive.uprotocol - up-rust" /></a>
Requirements
How well is the project doing when it comes to Requirements e.g. defining, versioning and managing, traceability, coverage, etc? For more details on the needs for the different levels of the Requirements Criteria read its definition here .
<a href="https://metrics.eclipse.org/projects/automotive.uprotocol"><img src="https://metrics.eclipse.org/badges/automotive.uprotocol_up-rust_badge_requirements.png" alt="Requirements badge for automotive.uprotocol - up-rust" /></a>
Has a requirements traceability URL defined.
Testing
How well is the project doing when it comes to Testing e.g. defining, versioning and managing, traceability, coverage, types of tests etc? For more details on the needs for the different levels of the Testing Criteria read its definition here .
<a href="https://metrics.eclipse.org/projects/automotive.uprotocol"><img src="https://metrics.eclipse.org/badges/automotive.uprotocol_up-rust_badge_testing.png" alt="Testing badge for automotive.uprotocol - up-rust" /></a>
Has a tests traceability URL defined.
Documentation
How well is the project doing when it comes to Documentation e.g. types of documents depending on contents, versioning, etc? For more details on the needs for the different levels of the Documentation Criteria read its definition here .
This project has not registered any activity on the criteria.
Coding Guidelines
How well is the project doing when it comes to Coding Guidelines e.g. defining, adhering, managing issues etc? For more details on the needs for the different levels of the Coding Guidelines Criteria read its definition here .
This project has not registered any activity on the criteria.
Release process
How well is the project doing when it comes to Releases e.g. defining a process, versioning and managing, release notes, coverage etc? For more details on the needs for the different levels of the Release Process Criteria read its definition here .
This project has not registered any activity on the criteria.
OSS Best Practices
Is the project respecting OSS good practices files in their repositories? See also the legal documentation checker for more information.
<a href="https://metrics.eclipse.org/projects/automotive.uprotocol"><img src="https://metrics.eclipse.org/badges/automotive.uprotocol_up-rust_badge_oss_best_practices.png" alt="OSS Best Practices badge for automotive.uprotocol - up-rust" /></a>
Repo up-rust has some of the recommended files.
Found categories: AUTOMATION, CONTRIBUTING, README, BUILD, LICENSE, NOTICES, CONDUCT