Project EVE - Stage 3 - 2026-11-04

Project EVE - Stage 3 - 2026-11-04


Completed by:  Renê de Souza Pinto, ZEDEDA

Submitted to TAC Mail List: 2026/11/04

Presented on TAC Weekly Call: 2026/11/04


 

Below is a self-assessment submitted by TSC Chair/Maintainers of the Project. Comments/questions/feedback is welcome either a) in the Comments at the bottom of the page or b) during the TAC call when information is presented

Stage 1: At Large Projects 

Stage 2 and Stage 3 Projects also requested to complete this section, as PLD acceptance criteria requires meeting current as well as prior stage requirements

Stage 1 Criteria (from the PLD)

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Stage 1 Criteria (from the PLD)

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations

Meets

Erik Nordmark, Doug Larson (IBM)

The typical IP Policy for Projects under the LF Edge Foundation is Apache 2.0 for Code Contributions, Developer Certificate of Origin (DCO) for new inbound contributions, and Creative Commons Attribution 4.0 International License for Documentation. Projects under outside licenses may still submit for consideration, subject to review/approval of the TAC and Board.

Meets

Using Apache 2.0, DCO, CCA4.0 - Technical Charter

Upon acceptance, At Large projects must list their status prominently on website/readme

Meets

https://www.lfedge.org/projects/eve/

 

Stage 1 Projects, please skip to Additional Information Requested from All Projects

Stage 2: Growth Stage

Stage 3 Projects also requested to complete this section

Stage 2 Criteria (from the PLD)

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Stage 2 Criteria (from the PLD)

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Development of a growth plan (to include both roadmap of projected feature sets as well as overall community growth/project maturity), to be done in conjunction with their project mentor(s) at the TAC.

Meets

Feature Roadmap

The project creates a build every two weeks (for every sprint) and an LTS release twice a year.

In this review period: 16.0.0-lts (January 2026) and 17.0.0-lts (July 2026), plus 22 bi-weekly feature releases (16.1 to 17.10). 18.0.0-lts is targeted for November/December 2026.

Document that it is being used in POCs.

Meets

Project EVE has been used in various POCs and is in large-scale production use, with 15,000+ EVE deployments in the field. See https://github.com/lf-edge/eve/blob/master/ADOPTERS.md

Demonstrate a substantial ongoing flow of commits and merged contributions.

Meets

Review period: October 23, 2025 to October 30, 2026, compared with the previous 12 months, both measured the same way from git history and the GitHub API across 12 EVE repositories (plus eve-kernel PRs):

  • 2,103 commits on main branches, up 78% (1,181); 3,665 including stable branches (1,714)

  • 1,892 merged PRs, up 82% (1,041)

  • 569 backport PRs to LTS stable branches, up 124% (254)

  • About 26 human commit authors in both periods; 4 new contributors this year

Note: previous reviews quoted LFX Insights totals (5,323 commits from 48 contributors in 2025), which count branches, the kernel fork and reviewers differently, so they are not directly comparable with the numbers above.

Demonstrate that the current level of community participation is sufficient to meet the goals outlined in the growth plan.

Meets

Yes. Throughput nearly doubled with a stable contributor base (about 80% of last year's authors are still active), and the project delivered two LTS releases on schedule.

Review capacity is the main constraint: human reviewers went from 29 to 23 and the median time to first review from about 1 hour to about 12 hours. We added AI-assisted PR and security review in CI and refreshed CODEOWNERS to spread the load.

Demonstrate evidence of, or a plan for, interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects).

Meets

  • Margo: LF Margo support is integrated in EVE-OS (Compose and Helm workloads) and was demonstrated at the Margo plugfests in March and July 2026.

  • Earlier interoperability work with EdgeX, CNCF SPOS WG, Akraino, FDO, Fledge and Open Horizon.

  • Continuing to support the LF Edge Sandbox.

 

Stage 2 Projects, please skip to Additional Information Requested from All Projects

Stage 3: Impact Stage

Criteria

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Criteria

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Have a defined governing body of at least 5 or more members (owners and core maintainers), of which no more than 1/3 is affiliated with the same employer. In the case there are 5 governing members, 2 may be from the same employer.

 Meets

TSC is currently at 5 members across 3 companies. From https://github.com/lf-edge/eve/blob/master/CONTRIBUTING.md:

Have a documented and publicly accessible description of the project's governance, decision-making, and release processes.

 Meets

TSC and committer election process, and release process https://github.com/lf-edge/eve/blob/master/CONTRIBUTING.md

Have a healthy number of committers from at least two organizations. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project.

 Meets

Currently 6 committers across 3 organizations. From https://github.com/lf-edge/eve/blob/master/MAINTAINERS.md

  • Avi Deitcher avi@deitcher.net

  • Erik Nordmark erik@zededa.com

  • Milan Lenco milan@zededa.com

  • Renê Pinto rene@zededa.com

  • Roman Shaposhnik rvs@apache.org

  • Shahriyar Jalayeri shahriyar@zededa.com

Changes since the last review: Shahriyar Jalayeri joined (October 2025); Roman Penyaev stepped down (May 2026).

Establish a security and vulnerability process which at a minimum includes meeting ("Met" or "?") all OpenSSF best practices security questions and SECURITY.md .

Meets

OpenSSF Best Practices: Passing (164%; silver criteria 64% met). See https://www.bestpractices.dev/en/projects/4746

OpenSSF Scorecard: 8.2 / 10 (October 2026).

Vulnerability management process, rewritten in 2026 to be clear to reporters, project members and adopters, and to meet the EU Cyber Resilience Act (CRA):

  • SECURITY.md: how to report; acknowledgment and analysis within 3 business days; 90-day disclosure timeline; safe harbor and scope. All EVE repositories point to it.

  • docs/VULNERABILITY-HANDLING.md: triage, commitments per severity, embargo and two-week vendor pre-notification, CVE assignment (GitHub as CNA) and publication through GitHub security advisories.

  • docs/RELEASE-SUPPORT.md: 24 months of security fixes for each LTS line, with stated end dates.

  • CRA: Linux Foundation stewardship statement; actively exploited vulnerabilities are reported to the LF steward on the 24h/72h clock.

  • Security documentation checked against the code and extended (docs/SECURITY-ARCHITECTURE.md); OpenSSF Security Insights file added (OSPS Baseline controls passed 16 → 20).

Other security work:

  • 25 CVE-fix PRs in this review period, mostly kernel backports

  • Releases signed with keyless cosign; per-variant SBOM published as a release asset

  • GitHub Actions pinned to hashes, Zizmor workflow audit, security-focused AI review on every PR

Demonstrate evidence of interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects).

 Meets

  • Margo: LF Margo support is integrated in EVE-OS (Compose and Helm workloads) and was demonstrated at the Margo plugfests in March and July 2026.

  • Earlier interoperability work with EdgeX, CNCF SPOS WG, Akraino, FDO, Fledge and Open Horizon.

  • Continuing to support the LF Edge Sandbox.

Adopt the Foundation Code of Conduct.

Meets

At https://lf-edge.atlassian.net/wiki/x/BYDyCQ and also referenced in https://lf-edge.atlassian.net/wiki/download/attachments/14583946/Technical Charter -- Enterprise Cyber-Physical Edge Virtualization Engine Project FINAL 2-12-19.pdf?version=1&modificationDate=1557623052344&cacheVersion=1&api=v2

Explicitly define a project governance and committer process. This is preferably laid out in a GOVERNANCE.md file and references a CONTRIBUTING.md and OWNERS.md file showing the current and emeritus committers.

Meets

TSC and committer election process, https://github.com/lf-edge/eve/blob/master/CONTRIBUTING.md Owners in https://github.com/lf-edge/eve/blob/master/MAINTAINERS.md

 

Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website).

Meets

https://github.com/lf-edge/eve/blob/master/ADOPTERS.md

Additional Information Requested from All Projects

Additional Information Requested from All Projects

Supporting Data (if needed, include links to specific examples)

Additional Information Requested from All Projects

Supporting Data (if needed, include links to specific examples)

Intention for the upcoming year (Remain at current stage OR advance towards the next Stage)

Remain at stage 3

Include a link to your project’s LFX Insights page. We will be looking for signs of consistent or increasing contribution activity. Please feel free to add commentary to add color to the numbers and graphs we will see on Insights.

https://insights.linuxfoundation.org/project/project-eve?repos=lf-edge-runx,lf-edge-eve-libs,lf-edge-eve-build-tools,lf-edge-eve-api,lf-edge-adam,lf-edge-eden,lf-edge-eve-tools,lf-edge-eve,lf-edge-eve-tpmea

Contribution activity increased: commits and merged PRs nearly doubled compared with the previous 12 months (see the Stage 2 section above). The contributor base is stable at about 26 commit authors.

How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.)

Currently six maintainers in https://github.com/lf-edge/eve/blob/master/MAINTAINERS.md

  • Avi Deitcher avi@deitcher.net

  • Erik Nordmark erik@zededa.com

  • Milan Lenco milan@zededa.com

  • Renê Pinto rene@zededa.com

  • Roman Shaposhnik rvs@apache.org

  • Shahriyar Jalayeri shahriyar@zededa.com

What do you know about adoption, and how has this changed since your last review / since you joined the current Stage? If you can list companies that are end users of your project, please do so. (Feel free to link to an existing ADOPTERS file if appropriate.)

How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.)

Goals from the 2025 review, Q3/Q4 2025 release:

  • EVE 16.0.0-lts release (done, January 2026)

  • k3s, KubeVirt and Longhorn in eve-k (done)

  • Network configuration changes via Local Profile Server (done)

  • Migration to kernel 6.12 LTS (done)

  • EVE evaluation image (done)

  • Hardware inventory report to the controller (done)

  • PCR prediction (in progress, PR #4578)

  • Attestation-enforced EVE update (in progress, PR #4578)

Q1/Q2 2026 release:

  • Port-based network access control, IEEE 802.1X (done)

  • Flexible TPM policy configuration (done)

  • NVIDIA JetPack 7.0 integration (done, JetPack 7.1)

  • Initial Margo support (done, shown at the Margo plugfests)

  • eSIM support (partial)

  • Real-time workloads on EVE (partial)

  • EVE update for air-gapped environments (partial)

  • Dual-SIM (DSSS) support (postponed)

What are the current goals of the project? For example, are you working on major new features? Or are you concentrating on adoption or documentation?

Goals for 2026/2027 (see also the Feature Roadmap):

  1. Release EVE 18.0.0-lts, targeted for November/December 2026

  2. AI platform devices: support NVIDIA Grace Blackwell (GB10, GB300); one EVE-OS update brings matching NVIDIA kernel, drivers, libraries and tools

  3. AI workloads on eve-k: keep building on eve-k to deploy and run LLMs and other AI models at the edge, on single nodes and clusters

  4. Embedded edge AI: support Qualcomm IQ8 and IQ9 platforms

  5. Continue integration and compliance work for the EU Cyber Resilience Act (CRA)

  6. Secure/verified boot as an option, alongside PCR prediction and attestation-enforced updates

  7. Additional real-time support, including completing CPU isolation

How can LF Edge help you achieve your upcoming goals?

  • Partner with LF Edge projects: connect us with Open Horizon, Fledge, EdgeX, InstantX and others to build joint integrations, with EVE-OS as the secure edge platform their workloads run on.

  • Grow the EVE community: bring EVE to new users and contributors through LF Edge events, webinars and blog posts, and introduce us to member companies building edge solutions.

  • A path to CNCF: eve-k is built on k3s, KubeVirt and Longhorn; a channel to raise questions with CNCF, such as long-term support for these components, would help us plan.

Do you think that your project meets the criteria for the next Stage?

We are already at stage 3

Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.)

  • Margo plugfests (March and July 2026): showed LF Margo support integrated in EVE-OS, for Compose and Helm workloads.

  • Transform events in Houston and Frankfurt (September/October 2026): use cases and deployments of EVE-OS.

Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available).

We did use it when the project started since it didn’t exist at the time. However, we have done all of the items in that checklist.

Please review, and update if needed, your Project entry on the Existing Project Taxonomy page, modifying the Last Updated / Reviewed date in the header.

Updated on November 18, 2024

Please share a LFX security report for your project in the last 30 days

https://security.lfx.linuxfoundation.org/#/a092M00001IV4DuQAL/overview

https://security.lfx.linuxfoundation.org/#/a092M00001IV4DuQAL/vulnerabilities

Note potential confusion/overlap due to shared lf-edge GH organization; see https://projectadmin.lfx.linuxfoundation.org/project/a092M00001IV4DuQAL/tools/security/overview