📢 Important Community Update: Migration of All Inji Repositories to the New GitHub Organization Begins Today

, , , ,
1

Dear MOSIP Community,

We are excited to announce an important structural update for the Inji ecosystem.
Starting today (24th Dec 2025), we are initiating the migration of all Inji-related GitHub repositories from the mosip organization to a new, dedicated Inji GitHub organization as part of our long-term plan to streamline Inji’s governance and maintainability.

Why This Migration?

To better support the rapid growth of the Inji ecosystem, we are transitioning Inji into its own GitHub organization.

This migration will:

  • Establish Inji as an independently maintained, clearly identifiable product suite
  • Streamline contributions from countries, SIs, and external partners
  • Provide clarity across Issuance, Wallet, Verify, SDKs, and libraries
  • Prepare Inji for long-term scalability and ecosystem expansion

This is an infrastructure-level reorganization—no functional changes to your workflow.

Migration Plan (High-Level)

  • Migration begins today(24th Dec 2025) with the movement of few initial repositories
  • Additional repositories will be migrated in phases
  • All Inji repositories will be moved under the new organization:

Inji Github

  • The community will receive updates after each migration phase
  • A final notification will be shared once all repositories are fully transitioned

What Is Changing?

This marks the first phase of the multi-step migration. Over the coming days and weeks, the remaining Inji repositories will move from:

MOSIP Github
to
Inji Github

This announcement is to keep the community informed as the reorganization begins.

No Impact On Your Current Work

Your development workflow will continue uninterrupted:

  • Existing clone URLs will auto-redirect
  • All commits, tags, issues, and pull requests remain intact
  • All CI/CD pipelines and submodules will continue to function normally
  • No breaking changes or repository restructuring at this stage

This is purely an organizational migration, not a code or functionality change.

Repositories Planned for Migration

The following repositories are part of the migration roadmap:

  1. inji-config
  2. Mimoto
  3. Inji Web
  4. Inji Mobile (inji-wallet)
  5. Inji Verify
  6. Inji Certify
  7. digital-credential-plugins
  8. Pixelpass (Kotlin + JS)
  9. VC Verifier (Kotlin)
  10. OpenID4VP (Kotlin)
  11. VC Renderer (Kotlin + JS)
  12. Tuvali (Kotlin)
  13. Tuvali (iOS)
  14. VC Renderer (Swift)
  15. VCI Client (Kotlin)
  16. VCI Client (Swift)
  17. OpenID4VP (Swift)
  18. Pixelpass (Swift)
  19. Secure Keystore (Kotlin)
  20. Secure Keystore (Swift)
  21. Inji Mock Services

This is an ongoing migration effort, and additional repositories will continue to move in batches.

:handshake: Need Help?

If you encounter any issues or have questions regarding repository access after migration, please reach out:

:e_mail: community.mosip.io
:speech_balloon: GitHub Discussions (coming soon under the new organization)

:star: Thank You

We appreciate your continued support as Inji evolves into a more modular, scalable, and globally interoperable verifiable credential ecosystem.
Together, we are building a secure and inclusive ecosystem for Verifiable Credentials.

Warm regards,
Sanchi Singh
Product Owner – Inji
On behalf of the Inji Team

3

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.