Community Advisory: Migration of Inji relate artifacts publish from MOSIP related repositories to dedicated Inji related repositories

Dear Community Members,

As part of the transition from the MOSIP GitHub organization to the dedicated Inji GitHub organization, we are updating our package publishing namespaces and repository configurations to strengthen consistency, governance, and long-term maintainability.

:white_check_mark: What’s Changing?
All new releases of Inji-related libraries will now be published under:

  • NPM: @injistack/*
  • Maven: io.inji:*

This change is effective immediately. Earlier packages published under MOSIP namespaces will remain available but will no longer receive patches or updates.

:warning: Impact for Existing Integrations

  • Projects that rely on older NPM packages under MOSIP namespaces will not receive further patches.

  • To access updates and fixes, consuming applications must upgrade to the new:
    NPM: @injistack/<package>
    Maven: io.inji:<package>

  • Some previously issued credentials may show verification warnings due to the older mosip.github.io context URLs.

  • To maintain backward compatibility, we are restoring the necessary GitHub Pages under the MOSIP org to temporarily serve the old context and DID documents.

  • A README will be added at the old location, indicating the migration to the INJI organization to avoid community confusion.

:pushpin: Recommended Action for All Developers

Please update your build configurations to use:

NPM → @injistack/
Maven → io.inji:

Follow the Inji GitHub organization for updates:
:point_right: Inji Github

:hammer_and_wrench: Additional Upcoming Changes (Advance Notice)

  • Over the next 1–2 weeks, we will also:
  • Publish SonarCloud reports to the new Inji project space
  • Publish Helm charts to the Inji charts repository
  • Publish Docker images under the injistack DockerHub organization

An additional advisory will be issued once these transitions are complete.

:page_facing_up: Deprecated Notice (for mosip/inji-config repository)

Deprecated Notice:
This repository has been migrated to the new Inji GitHub organization and is no longer maintained under MOSIP.

It is temporarily retained only to serve previously published GitHub Pages required for the verification of older credentials.

Please refer to the updated repository here: GitHub - inji/inji-config: Contains configurations for Inji stack

All new development, patches, and configuration updates will occur exclusively under the Inji organization.

:handshake: Support
If you face issues upgrading your dependencies or verifying credentials, please raise an issue in the Inji GitHub repositories or reach out via community support channels.
Thank you for your cooperation as we evolve into a more secure, consistent, and unified Inji ecosystem.

Best regards,
On behalf of the Inji Team

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