[Backend] Replace the static Cargo dependency registry with a maintainable update source

[ayomideadeniran]

🚀 Feature Overview

Improve the dependency-update service so its version recommendations are maintainable, typed, and clearly separated from live update execution.

🛠️ Implementation Requirements

• Remove the ts-nocheck directive from the dependency-update service.
• Extract the registry into a documented provider or configuration layer.
• Add a refresh strategy or clearly label the registry as curated snapshot data.
• Improve semantic-version edge-case handling and tests.
• Ensure no external registry failure breaks the rest of the application.

🔧 Technical Specifications

Node.js, TypeScript, Cargo.toml parsing, semantic versioning, Jest.

✅ Acceptance Criteria

• Dependency-update service builds without ts-nocheck.
• Version comparison handles common prerelease and malformed input safely.
• Registry data has a documented ownership and update strategy.
• Unit tests cover simple dependencies, inline tables, unknown packages, and version edge cases.
• Service failures return actionable errors.

🎓 Difficulty Level

Intermediate — requires TypeScript parsing and dependency-management knowledge.

⏱️ Timeline

ETA: 2 days

[xtep103]

@xtep103 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainer,I’m interested in contributing to the task and can ensure timely delivery with clean implementation.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @xtep103 to this issue.

[sudo-robi]

@sudo-robi has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainer I'm a full stack developer and smart contract developer and auditor let me help you resolve this issue and I assure you it will be thoroughly done neatly as I have seen my way to solve the issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @sudo-robi to this issue.

[Tobiloba0]

@Tobiloba0 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hi maintainer, I would like to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Tobiloba0 to this issue.

[Godswillopeyemihub]

@Godswillopeyemihub has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi! I'd like to work on this issue.

I'm a software engineer with hands-on experience in testing, debugging, and building reliable features across the stack. I'm confident I can take this on and deliver a solid, well-tested solution that follows the project's existing conventions.

I'll make sure to cover the core functionality as well as relevant edge cases to keep things reliable and regression-resistant.

Let me know if I can get started, and I'll provide updates as I progress.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Godswillopeyemihub to this issue.

[drips-wave]

Congratulations, @xtep103! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @xtep103: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊