2025 Identus Annual Review #91
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,91 @@ | ||
| --- | ||
| layout: default | ||
| title: 2025 Annual Review Identus | ||
| parent: 2025 | ||
| grand_parent: Project Updates | ||
| --- | ||
|
|
||
| ## Project Health | ||
|
|
||
| LF Decentralized Trust Identus [LFX Insights Dashboard](https://insights.lfx.linuxfoundation.org/foundation/lf-decentralized-trust/reports/contributors?project=identus&bestPractice=false&dateFilters=Last%20Year&dateRange=2024-01-01%20to%202024-12-31&compare=PP&granularity=month&hideBots=true&repository=all) | ||
| The project is relatively new to the LF Decentralized Trust Ecosystem and is mainly supported by the IOG maintainers. | ||
| At the same time, over the past year, we have seen several new contributors and evidence of usage of the Identus platform by other companies: | ||
| - https://socious.io/, Socious production use case. | ||
| - https://ahau.io/, Ahau PoC. | ||
| - https://blocktrust.dev/, - identity wallet. | ||
|
There was a problem hiding this comment. This looks great. Please consider adding these references to an |
||
|
|
||
| We currently utilize two Discord servers: the LF Decentralized Trust Discord and the private Identus Discord server. | ||
| The Identus Discord has seen significantly more engagement. | ||
|
There was a problem hiding this comment. Just to clarify, what do you mean by "private"? |
||
| Since January 2024, our membership has grown from 258 to 476 members. | ||
| On average, there are 348 activities across various channels monthly, with about 39 users online daily. | ||
|
|
||
| ## Maintainer Diversity | ||
|
|
||
| There are currently 10 maintainers from IOG and other companies. | ||
|
|
||
| The MAINTAINERS.md file is up to date and can be found [here](https://github.com/hyperledger/identus/blob/main/MAINTAINERS.md) | ||
| The `identus-maintainers` [team](https://github.com/hyperledger/governance/blob/main/access-control.yaml#L625-L655) includes around 10 members from IOG and other companies. | ||
|
|
||
| The number of active maintainers has decreased due to restructuring the Atala Team at IOG. | ||
| However, the diversity of maintainers has increased over the past six months, with more companies contributing to the project. | ||
|
|
||
| ## Project Adoption | ||
|
|
||
| Several companies are using the Identus project for prototyping and production use cases. | ||
|
|
||
| The following companies are using the project: | ||
| - https://socious.io/, Socious production use case. | ||
| - https://ahau.io/, Ahau PoC. | ||
| - https://blocktrust.dev/, - identity wallet. | ||
|
There was a problem hiding this comment. This list seems redundant. You can just add a reference to the "Project Health" section. Alternatively, you can refer to this list from the "Project Health" section. |
||
|
|
||
| Developers actively participate in the weekly meetings and consider using the Identus platform for their use cases. | ||
|
|
||
| ## Goals | ||
|
|
||
| ### Performance Against Prior Goals | ||
|
|
||
| The current project roadmap is public and can be found here: [Identus Roadmap](https://github.com/orgs/hyperledger/projects/48) | ||
|
|
||
| During the last six months, the project has achieved the following goals: | ||
| - Connectionless Issuance and Verification of VC via DIDCommV2 | ||
| - DID Prism AnonCreds method to resolve the resources from the DID Prism URL (for the schema and credential definition) | ||
| - Crypto Agility of the DID Prism Method (added Ed25519 cryptography suite) | ||
| - Transitioning the project from the IOHK to the LF Decentralized Trust organization | ||
| - OID4VCI specification implementation in the Cloud Agent and SDKs (for JWT VC only) | ||
| - Major refactoring: | ||
| -- a. improved error handling in the Cloud Agent, the Mediator, and SDKs, | ||
| -- b. added Problem Report protocol to other protocols, | ||
| -- c. Background jobs are replaced with the message queue (in-memory or Kafka) | ||
| - SD-JWT-VC implementation in the Cloud Agent and SDKs | ||
| - Status List revocation implementation in JWT VC | ||
| - Improved documentation with the Quick Start Guide and Tutorials | ||
|
|
||
| The roadmap is actively discussed with the community members in the GitHub [Discussions](https://github.com/hyperledger/identus/discussions) | ||
|
|
||
| ### Next Year's Goals | ||
|
|
||
| The project has the following strategic goals for the next year: | ||
| - Reduce maintenance cost and complexity of the Identus platform | ||
| - Increase the Identus platform adoption by the developers and companies | ||
| - Improve the platform interoperability with other SSI platforms | ||
| - Improve the platform documentation and tutorials | ||
|
|
||
| The following features are planned for the next year, among others: | ||
| - Cardano Identus VDR | ||
| - Bring Issuance capabilities to the SDKs | ||
| - Continue with UAS Wrapper implementation | ||
| - Pollux Plugin abstraction SDK | ||
| - OIDC specifications for the SSI: OID4VCI, OID4VP, SIOP2.0 | ||
| - Authentication using the PRISM DID method | ||
|
|
||
| ### Help Required | ||
|
|
||
| LF Decentralized Trust can help with the following: | ||
| - Promote the Identus project within the LF Decentralized Trust community | ||
| - Help with the workshops and hackathons | ||
| - Help to collaborate with the LF Decentralized Trust Aries project as the Identus platform leveraging the Aries specs and protocols | ||
|
There was a problem hiding this comment. One suggestion is to have maintainers from your project participate in Aries meetings, and invite their maintainers to participate in yours. Avenues for collaboration and code-sharing may open up that way. |
||
|
|
||
|
|
||
| ## Project Lifecycle Status Recommendation | ||
|
|
||
| The Identus is a reasonably new incubation project in the LF Decentralized Trust Ecosystem and should remain so. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The LFX Insights numbers are very low compared to other projects: https://insights.lfx.linuxfoundation.org/foundation/lf-decentralized-trust/overview/best-practice-score?project=identus&routedFrom=Github&bestPractice=false&repository=all&dateFilters=Last%2012%20Months&dateRange=2024-01-24%20to%202025-01-23&compare=PP&granularity=month&hideBots=true. I guess this is because only the
governancerepo has been migrated to the new org? Do you have a plan for migration of the rest sometime soon? I don't see any comments about this further below.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, it looks like you don't have the OpenSSF scorecard configured for Identus: https://scorecard.dev/viewer/?uri=github.com%2Fhyperledger%2Fidentus. Please keep in mind that the OpenSSF Scorecard and the OpenSSF Best Practices badges must be configured for all projects. Soon, TAC project reviews will routinely consider scores from here and from the LFX Insights. For reference on how to configure badges, please see lines 2-3 from the Cacti README file: https://raw.githubusercontent.com/hyperledger-cacti/cacti/refs/heads/main/README.md.