Health check depth for database and Horizon

[greatest0fallt1me]

Description

Extend /health to report dependency readiness (database ping, Horizon reachability) for orchestrators.

Requirements and context

• Fast fail for liveness versus slower readiness semantics documented.

Suggested execution

Fork and branch

Fork the repo and create a branch:

git checkout -b feature/health-dependencies

Implement changes

• Update Creditra-Backend/src/routes/health.ts.
• Tests in src/__tests__/health.test.ts and tests/health.test.ts.

Test and commit

Run tests, cover edge cases, and attach test output plus security or ops notes (auth, PII, Stellar keys) in the PR.

Run tests

npm test

Example commit message

feat(health): dependency checks in health endpoint

Guidelines

• Minimum 95% coverage on touched modules where applicable (npm test / coverage report).

• Clear documentation (OpenAPI openapi.yaml, README, and inline comments for non-obvious logic).

• Timeframe: 96 hours.

• Run npm run build or tsc if types change.

• Keep OpenAPI in sync with route behavior.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[ryzen-xp]

@ryzen-xp has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi maintainers 👋
I’m a blockchain developer with strong expertise in Stellar, Rust,TS and Stellar SDK integrations. I’ve worked on multiple Stellar-based smart contract and backend systems.

I understand the scope of this issue and can deliver a reliable, production-quality solution with proper tests and documentation.
Plz assign me !!

ETA: 12 hours

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

[drips-wave]

Congratulations, @ryzen-xp! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @ryzen-xp: 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 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @ryzen-xp as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully implemented the health check extensions for database and Horizon as requested. The PR #170 was merged by the maintainers, and the tests were updated to cover the new functionality.

😎 @ryzen-xp: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.