# WeBankBlockchain/WeIdentity

基于区块链的符合W3C DID和Verifiable Credential规范的分布式身份解决方案

Repository: https://github.com/WeBankBlockchain/WeIdentity
Canonical: https://ross.abutalabs.com/products/weidentity
Homepage: https://fintech.webank.com/weidentity
Language: Java
License: Apache-2.0
License Family: permissive
Topics: blockchain, distributed-identity, distributed, did, data-exchange, w3c, privacy-preserving, selective-disclosure, privacy-protection, identity, verifiable-credentials, verifiable-presentation, certificate, dpki, digital-signature, consortium, kyc, weidentity, weid, weid-java-sdk
Last push: 2025-04-18T03:31:37+00:00

## Health v2 (maintenance only)
Score: 30/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 17, release rhythm 8, longevity 100
- inputs: {"age_days": 2864, "days_push": 502, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1150, forks 175 (observed 2026-08-28T04:03:46.624200+00:00)

## What it is
WeIdentity is a blockchain-based distributed identity solution implementing W3C DID and Verifiable Credential specifications, developed by WeBank. It provides a Java SDK and REST service for on-chain identity registration, verifiable credentials, selective disclosure, and secure data exchange on the FISCO-BCOS platform.

## Use cases
- issue and verify digital credentials on a blockchain
- implement decentralized identity (DID) for users or things
- build a KYC verification flow with verifiable credentials
- enable selective disclosure of personal data with privacy protection
- map real-world identities to on-chain identities
- exchange data securely across institutions with access authorization

## When to choose
- you need W3C-compliant DID and verifiable credentials on FISCO-BCOS
- you are building consortium-blockchain identity or KYC infrastructure in Java
- privacy-preserving selective disclosure of credentials is required

## When to avoid
- you need identity on public chains like Ethereum or Solana
- your stack is not JVM/Java-based and the REST service does not fit
- you only need simple centralized authentication without blockchain

## Facets
- artifact type: library
- maturity: active
- function: auth, cryptography, security, sdk, privacy
- domain: blockchain, security, privacy, developer-tools, apis
- platform: jvm, self-hosted
- tags: decentralized-identity, did, verifiable-credentials, w3c-standards, selective-disclosure, kyc, fisco-bcos, digital-signature, consortium-blockchain, blockchain

## Member repositories
- WeBankBlockchain/WeIdentity (main) score 30

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:46.624200+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:33:39.376863+00:00, confidence not recorded.
  - readme: https://github.com/WeBankBlockchain/WeIdentity (fetched 2026-08-28T04:03:46.624200+00:00, sha 6882df3b1167)
- Data as of 2026-08-30T08:39:29.467469+00:00.