/
EdgeX Foundry - Stage 3 - 2025-10-08

EdgeX Foundry - Stage 3 - 2025-10-08

Completed by:  James Butcher, IOTech Systems

Submitted to TAC Mail List:  2025/10/08

Presented on TAC Weekly Call:  2025/10/08 (Meeting Recording)

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

Martin Kronberg (IBM), Fukano Haruhisa (Fujitsu) + Brad Corrion (IOTech)

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

  • EdgeX is an Apache 2.0 license project.  We require all contributions comply with this license agreement as stated in our Wiki below: EdgeX contributors guide

  • EdgeX policy to review new libs, modules, etc. brought into the project to insure anything we use (or is used indirectly by modules we bring in) is compliant with this license. https://wiki.edgexfoundry.org/display/FA/Vetting+Process+for+3rd+Party+Dependencies

  • We also conduct code scans regularly (with each PR) for any license compliance issues

  • EdgeX is proud to have successfully handled challenges arising from a trend of some third-party components changing their open-source license policy (e.g. Redis, Vault, Consul).  These are now all phased out of the EdgeX codebase for Apache 2.0 compatibles projects – e.g. OpenBao (new LF project), MQTT, Core-Keeper, etc

 

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

Meets

Displayed proudly on EdgeX wiki:

image-20240923-184424.png

… and on the EdgeX website:

image-20251006-091338.png



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)

Demonstrate regular project leadership (typically TSC) meetings.  Project leadership should meet monthly at a minimum unless there are extenuating circumstances (ex: holiday period)

Meets

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

  • Open and collaborative release planning meetings held once or twice per year

  • We maintain a short-term roadmap for 1-2 releases ahead and maintain a longer term backlog.  The next couple of releases are documented with pages in our Wiki (and you can see past release roadmaps) here:  https://wiki.edgexfoundry.org/display/FA/Roadmap

  • Minor fixes and enhancements are also captured in issues with each repository in Github.  Github tags are used to label bugs from enhancement requests and when appropriate are associated with a specific target release (e.g., "Palau" tags on the Technical WG Kanban project board here: https://github.com/orgs/edgexfoundry/projects/56 for an example).

Document that it is being used in POCs.

Meets

EdgeX is used in countless POCs worldwide so this list is actually more about production uses.

Demonstrate a substantial ongoing flow of commits and merged contributions.

Meets

Collected from LF Insights for the project since inception and for the last 12 months:

 

Total (since 2017)

Past 12 months

Active Contributors

1,130

136

Commits

37,930

2,074

Pull Requests

12,583

715

Around 30 different contributors per month:

image-20251006-104949.png

 

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

Meets

Already at stage 3. Demonstrated maturity by 14 successful project releases since April 2017 (usually 2 each year) and a strong number of contributors.

  • EdgeX 4.0 (“Odesa” was a new major release version, released on March 14th 2025)

    • The Latest Long Term Support (LTS) version with a 24 month community support cycle

On track for a further release this year: EdgeX 4.1 “Palau” by end of 2025

Demonstrate a willingness to work with (via interoperability, compatibility or extension) other LF Edge projects to provide a greater edge solution than what can be done by the project alone. 

Meets



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)

Meets

image-20251006-220004.png

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

Meets

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

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

Meets

The project has a well defined security & vulnerability process as defined here: https://lf-edgexfoundry.atlassian.net/wiki/spaces/FA/pages/11671699/Security

The LTS releases have have CVE patches applied to them, for example: https://lf-edgexfoundry.atlassian.net/wiki/spaces/FA/pages/11678726/Napa+3.1.1+Bug+Release+to+LTS with a patch releases planned for 4.0 shortly

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

Adopt the Foundation Code of Conduct.

Meets

  • For any significant community meeting such as the TSC meetings or meeting where we are inviting outside community to speak or observe are always preceded by the code of conduct and anti-trust policy statements.  To date, we have had no unacceptable behavior incidents that the project has been made aware of

  • EdgeX adheres to, follows and enforces the LF Edge Code of Conduct without addendum today.

https://wiki.edgexfoundry.org/display/FA/Code+of+Conduct

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

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

Meets

Our main repository contains the Adopter document (see https://github.com/edgexfoundry/edgex-go/blob/main/ADOPTERS.md )

We also highlight user, adopters and commercial interests of EdgeX on our Website.



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 Impact Project.

Plan to release a 4.1 minor release by end of year. The 4.0 release remains strong with our Apache 2.0 based licensing across all components and is LTS-supported until March 2027

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.lfx.linuxfoundation.org/foundation/lfedge/overview/github?project=edgex&routedFrom=Github&bestPractice=false&repository=all&dateFilters=Last%203%20Years&dateRange=2021-01-01%20to%202023-12-31&compare=PP&granularity=month&hideBots=true

image-20251006-125921.png

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

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.)

EdgeX users are now most often at the deployment stage but we are learning about new adopters all the time.   In addition to the companies that are participating in the construction and delivery of EdgeX (IOTech, Intel, Eaton, Schneider Electric, Danfoss, Yiqisoft), the following companies have announced (and presented) on EdgeX adoption:

  • Canonical, IOTech, HP, Thundersoft, Jiangxing Intelligence, Tibco, Accenture, HCL Tech, BSI, Advantech, BMC, Cloud2Go, Tuxmart

Many organizations have adopted, adopting or are considering the adoption of EdgeX and related products including:

  • Advantech Corporation, TP-Link Corporation, NEC Corporation, State Grid Corporation of China, Acuvate, HETONG Group, Ecolab China, CPIC (China Pacific Insurance Group), NetEase Technology, Fanmi Technology,

  • China Unicom (China United Network Communications Group) is a Chinese state-owned telecommunications operator. utilizes EdgeX Foundry to enable video analysis from cameras such as CCTV (closed-circuit television) systems and IPC (IP cameras) in its IoT deployments.

  • Coal Science Research Institute (Software Research division): the institute leverages the EdegX capabilities to develop data collection for underground equipment in the coal sector

Others who have adopted EdgeX and related products:

  • Large energy/oil company, multiple large BESS companies, large building automation companies, Shift Energy, large mining company, modern AgTech company, glass production company, brick production company, etc

  • The public EdgeX forum is a good indicator of users and evaluators of the technology: https://github.com/orgs/edgexfoundry/discussions

  • Statistics from the EdgeX website and documentation website tell positive story of consumption)

    • 1,641 users (2,333 sessions) of main website for Sep 2025

    • 2,097 users (4,774 sessions) of docs website for Sep 2025

    • World map of Top Countries by Sessions (last 12 months):

image-20251006-131759.png

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

Met or exceeded goals.  Over 9 million container downloads. 14 releases since 2017. Currently planning V4.1 and patch LTS release, all indicating the stability of EdgeX to the marketplace.

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?

  • The main aim continues to focus on enabling EdgeX deployments and massive scale out. Requested features for 4.1 included performance optimizations for data flow and convenience APIs to reduce even further the amount of code that users would have to maintain (e.g. delete all devices with a single function call)

  • Advanced security and new legislation (e.g. EU Cyber Resilience Act) putting more emphasis on security requirements. EdgeX reformed its Security Working Group to drive this. First task is an updated/completed Security Threat Model

  • Looking to continue to grow the user base with more publicly referenced adopters.

How can LF Edge help you achieve your upcoming goals?

Appreciate all help especially with marketing support and continued raising awareness of EdgeX on social media, news, etc. Amplifying the message of maturity, industry readiness, etc

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

N/A. We are at stage 3

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

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

This was developed after our project launched, but we already follow all steps.

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

Up to date

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

https://security.lfx.linuxfoundation.org/#/a0941000005osNnAAI/overview
Updates/validity checking may be required