Enable TypeScript noImplicitAny and eslint no-explicit-any

[meshackyaro]

Description

tsconfig.json sets "noImplicitAny": false, and .eslintrc.js sets "@typescript-eslint/no-explicit-any": "off". Both are currently used in real code: src/monitoring/health.controller.ts (getHealth(): Promise<any>), src/event-ingestion/event-processor.service.ts (value: any), src/auth/auth.guard.ts (handleRequest(err: any, user: any, info: any)), src/common/rate-limit/rate-limit.guard.ts (getIdentities(request: any), extractWallet(request: any), getRoute(request: any)), src/event-ingestion/event-ingestion.service.ts (parseEventValue(value: any): any, parseTopic(topic: any): string), src/stellar/soroban.helper.ts (isSimulationError(result: any)), and src/stellar/stellar.service.ts (account.balances.find((b: any) => ...)- ). Loosening both compiler and lint checks means real type errors in exactly the kind of request-parsing/RPC-response-parsing code that benefits most from static typing can slip through silently.

Component

Backend

Difficulty

🔴 Hard

Tasks

• Flip noImplicitAny to true in tsconfig.json and @typescript-eslint/no-explicit-any to "warn" (or "error") in .eslintrc.js
• Work through the resulting compiler/lint errors, replacing any with proper types or interfaces (e.g. typed Express Request, Soroban SDK response types) file by file
• Land the change incrementally if needed (e.g. per-directory // eslint-disable suppressions with follow-up tickets) rather than requiring one giant PR

Acceptance Criteria

• npx tsc --noEmit and npm run lint:check both pass with noImplicitAny: true and no-explicit-any enabled
• No behavior changes — this is a types-only cleanup verified by the existing test suite continuing to pass

Estimated Time

3-4 days

[Peolite001]

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

i would love to work on this issue

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

[macsonfleek]

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

Hi Maintainer! Please assign me to this issue, I would love to work on it

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

[flexocode442]

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

Hello, I’ve thoroughly read the issue description and understand the expected outcome. I’d love to work on it.

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

[Ukorstack]

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

I’m ready to handle this issue efficiently and ensure the final PR meets the project standards. Kindly assign it to me.

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

[TS-mfon]

@TS-mfon has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

GM

i'm a blockchain developer

please can i work on this issue

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

[Biokes]

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

Hi maintainer,
I am willing to work on this issue.

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

[drips-wave]

Congratulations, @Biokes! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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