General Registry repository URL mismatch after migration to JuliaHealth

[kosuri-indu]

Hey, As part of a NumFOCUS Small Development Grant Project Work, I am currently conducting an ecosystem-wide audit of the JuliaHealth organization to better understand documentation, CI, maintenance and registry metadata consistency across packages.

During this audit, I noticed a repository URL mismatch for this package in the Julia General Registry.

What's the issue?

• The package is currently maintained under the JuliaHealth organization.
• However, the General Registry entry still points to the old / non-JuliaHealth repository URL.
• While GitHub redirects currently work, mismatched registry metadata can still lead to confusion and may surface issues when:
  • Tagging new releases
  • Registering future versions
  • Discovering the canonical repository

This mismatch was identified programmatically as part of the audit results: Registry Mismatches

Why this matters

As said earlier, even if GitHub redirects currently work, registry metadata is ideally expected to:

• Point directly to the canonical repository
• Reflect current ownership and maintenance location
• Avoid future issues with Registrator or tagging workflows

Proposed next steps

I wanted to check with you (@jakubMitura14 @JanZubik @MarijaGijic) before proceeding:

• ✅ Would you be okay with updating the General Registry repo URL to point to the JuliaHealth repository?
• 🔧 If yes, would you prefer:
  • That I open a PR to the General Registry to fix this, or
  • That you handle the registry update directly?

I am happy to take care of the registry PR if that's helpful.

~ indu