How sphereon-opensource/ssi-sdk works
Project type and purpose
• This is a TypeScript monorepo (managed with Lerna/pnpm/turbo) providing a Self-Sovereign Identity SDK.
• It delivers modular “plugins” for Veramo-style agents: core utilities (ssi-sdk-core, ssi-types), persistence (data-store, kv-store), domain features (OID4VCI, SIOPv2/OID4VP, Presentation Exchange, Contact Manager, Issuance Branding, QR-Code generation, Well-known DIDs, MS Entra support, etc.), plus standalone REST-API “microservices” and a CLI.
File structure
• Root: configuration (tsconfig.*, lerna.json, turbo.json, CI workflows), scripts, build/test configs.
• packages/: dozens of sub-packages, each with its own README, src/, tests, schema, agent.yml.
• Categories (implied by README):
– Generic Core: ssi-types, ssi-sdk-core
– Persistence: data-store (TypeORM), kv-store
– Domain Plugins: presentation-exchange, oid4vci-issuer, siopv2-* , wellknown-did-*, contact-manager, issuance-branding, qr-code-generator, etc.
– REST API Layers: *-rest-api packages (oid4vci-issuer-rest-api, siopv2-rp-rest-api, contact-manager-rest-api, pd-manager-rest-api, public-key-hosting, etc.)
– CLI: packages/dev/bin and src
Extract insights from the README
• Confirms plugin categories and their intended usage contexts (issuer, holder, verifier, Relying Party, webapp, mobile).
• Notes that most plugins plug into an “Agent” runtime (NodeJS or React-Native), with some also exposing a REST API (Express).
• Underlying persistence uses TypeORM (data-store) or key-value abstractions (kv-store).
Elements
– Plugin → Core (integration)
– REST API → Plugin → Persistence → External Resolver
– CLI → Core & Plugins
– Core libraries (e.g., blue)
– Domain plugins (green)
– Persistence (orange)
– REST API (purple)