Most Transparent Development Process: in-depth analysis of which EUDI Wallet implementations offer the greatest openness in code, documentation, and public participation.
Top Recommendations
#1: Germany
App: AusweisApp
OpenCoDE GitLab, public architecture docs, consultation process
#2: Netherlands
App: NL-wallet
Code on GitHub, Figma designs public
#3: France
App: France Identité
Some public documentation
#4: Belgium
App: MyGov.be
Standard government transparency
#5: Italy
App: IT-Wallet
AGID publishes updates
Why Transparency Matters for Digital Identity
When a government asks citizens to entrust their most sensitive personal data to a digital system, transparency is not optional but a fundamental requirement for building public trust. The EUDI Wallet will store identity documents, health credentials, educational certificates, and potentially financial information. Citizens have every right to understand exactly how this data is stored, processed, and protected.
Open source development provides the strongest form of transparency. When the wallet's source code is publicly available, independent security researchers, privacy advocates, and competing governments can verify that the software does what it claims and nothing more. This is especially important for digital identity systems, where hidden backdoors or surveillance capabilities would devastate public trust.
Beyond code transparency, process transparency matters equally. Public consultation periods, published architecture decision records, and open issue tracking allow citizens and organizations to understand not just what was built but why specific design choices were made. Germany and the Netherlands excel in this area, maintaining public roadmaps and actively engaging with community feedback.
How We Evaluated Transparency
Our transparency scoring evaluates five dimensions: source code availability (is the code publicly accessible?), documentation quality (are architecture and design documents published?), community engagement (can external contributors participate?), audit accessibility (are security audit results made public?), and governance openness (are decision-making processes documented and consultative?).
Germany earned its near-perfect 98/100 score by excelling across all five dimensions. The AusweisApp code lives on OpenCoDE, Germany's official open-source platform. The BSI publishes detailed technical guidelines (TR-03127, TR-03128, TR-03130) documenting every aspect of the security architecture. Public consultations are held regularly, and security audit results are published.
The Netherlands earns 92/100 with a strong showing in community engagement. The NL-wallet project on GitHub has active issue discussions, accepts external contributions, and publishes Figma design files, making even the UX design process transparent. Logius, the responsible agency, maintains public documentation of architectural decisions and regularly publishes progress updates.
Key Features of Transparent Development
The most transparent EUDI Wallet implementations share several key features. First, they use established open-source hosting platforms (OpenCoDE for Germany, GitHub for the Netherlands) with built-in tools for issue tracking, code review, and version history. This creates an immutable record of every change made to the software.
Second, they publish not just the code but the context around it. Architecture Decision Records (ADRs) explain why certain technical choices were made. Threat models document what risks were considered and how they are mitigated. API documentation enables third-party developers to build integrations without reverse-engineering the system.
Third, truly transparent projects welcome external scrutiny. Bug bounty programs incentivize security researchers to find and report vulnerabilities responsibly. Public issue trackers allow anyone to report bugs or request features. Regular community calls give stakeholders a direct channel to the development team. These practices build a virtuous cycle where transparency leads to higher quality software.
Future Directions in Transparency
The European Commission increasingly recognizes transparency as a cornerstone of the EUDI Wallet ecosystem. The Architecture and Reference Framework (ARF) itself is publicly available, and the EU Large-Scale Pilots have committed to publishing their findings. There is growing momentum toward requiring all national EUDI Wallet implementations to meet minimum transparency standards.
One emerging trend is the use of reproducible builds, which allow anyone to verify that the published source code matches the actual application distributed through app stores. Germany is pioneering this approach with AusweisApp, and the Netherlands has expressed interest in implementing it for the NL-wallet.
Looking ahead, transparency will become a competitive differentiator. As citizens become more aware of digital privacy issues, they will gravitate toward wallets from countries that demonstrate genuine openness. Countries that embrace transparency early will benefit from stronger public trust, higher adoption rates, and a more engaged developer community contributing to the quality of their digital identity infrastructure.