⚠️ Android dependency-check failed (scheduled scan)

[github-actions]

The weekly Android dependency vulnerability scan failed.

This may mean a dependency now has a known CVSS >= 7.0 vulnerability, or the
scan itself failed for an unrelated reason (see the run log).

Workflow run: https://github.com/ethos-protocol/ethos-mobile/actions/runs/34117993006

Related: #178 (moved this job off the per-PR trigger after it repeatedly
hung for 1h+ without an NVD API key and got killed by the runner).

[ZacLou]

I’ll inspect the failing dependency-check run, identify the exact vulnerable dependency or scan failure, then fix it with a minimal version bump or scan-config change. I’ll verify the workflow passes and keep the PR scoped to this issue only, with a short note on the audited dependency and the verification command.

[Danitello123]

I’m a smart contract and full-stack developer who turns complex ideas into secure, production-ready blockchain code.
With strong skills in Rust and Solidity, I build systems that are fast, safe, and built to last.
My experience with the Stellar SDK lets me ship real-world Web3 solutions that actually move value.

[Iker2522]

I'd like to take this issue on!

I can investigate and resolve the failing Android weekly dependency vulnerability scan for ethos-mobile.

I will analyze the workflow run logs (#34117993006) to identify the specific trigger—whether it's a critical CVE in our Gradle dependency tree or a scanner/NVD rate-limiting failure. If a dependency exceeds the CVSS threshold, I will bump it to a secure release or patch the version catalog (libs.versions.toml). If it's a runner/API configuration issue, I will tune the scanner flags to ensure reliable execution.

I will verify the fix locally and trigger a workflow run to ensure the security scan passes cleanly without blocking mobile builds. PR ready in 12 hours. Closes #.

[guptakumarranjeet150]

Hi everyone,

I would love to take this on. My planned approach:

• Trace the regression in ethos-protocol/ethos-mobile causing ⚠️ Android dependency-check failed (scheduled scan) and implement a targeted, minimal fix.
• Add a reproduction test case to prevent any future regression.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[shobhamerabacha-star]

Hello @maintainers,

I would love to take this on. My planned approach:

• Trace the regression in ethos-protocol/ethos-mobile causing ⚠️ Android dependency-check failed (scheduled scan) and implement a targeted, minimal fix.
• Add a reproduction test case to prevent any future regression.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!