Eclipse Open Vehicle API

Activity - commits

There have been 37 commits made by 2 people on 2 repositories over the last 12 months.

Activity - issues

There have been 1 issues submitted by 1 people on 1 repositories over the last 12 months.

Activity - reviews

There have been 32 reviews submitted by 2 people on 2 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.openvehicle-api

Releases

Reviews

• Eclipse Open Vehicle API 2027.08 Progress (2027-08-04) – see review
• Eclipse Open Vehicle API 2026.08 Progress (2026-08-06) – see review
• Creation (2025-08-20) – see review

IP Lab requests

• 2025-12-10 - project/automotive.openvehicle-api/eclipse-openvehicle-api/openvehicle-api/f74e494a43e217020701291ba387383643471b07

Organization Settings

• GitHub organization: eclipse-openvehicle-api
• 2FA enforced: True
• Default workflow permissions: read

Branch Protections

This project has a total of 2 repositories in its associated GitHub organization eclipse-openvehicle-api . 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 .

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.

This project has not registered any activity on the criteria.

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 .

This project has not registered any activity on the criteria.

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 .

This project has not registered any activity on the criteria.

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.

Reuse this badge!

<a href="https://metrics.eclipse.org/projects/automotive.openvehicle-api"><img src="https://metrics.eclipse.org/badges/automotive.openvehicle-api_badge_oss_best_practices.png" alt="OSS Best Practices badge for automotive.openvehicle-api" /></a>