Android-Fixes for various stylings in the views.

[Bryan Malumphy (bmalumphy)]

No description provided.

[github-actions]

🟢 Test Coverage Report - @dittolive/ditto-chat-core

Overall Coverage: 88.31%

Metric	Coverage	Status
🟢 Lines	87.35%	green
🟢 Statements	87.35%	green
🟢 Functions	92.45%	green
🟢 Branches	86.1%	green

---

📊 View Detailed Coverage Report

ℹ️ Coverage Thresholds

• 🟢 Excellent (≥ 80%)
• 🟡 Good (60-79%)
• 🟠 Fair (40-59%)
• 🔴 Poor (< 40%)

[github-actions]

🟢 Test Coverage Report - @dittolive/ditto-chat-ui

Overall Coverage: 89.68%

Metric	Coverage	Status
🟢 Lines	92.05%	green
🟢 Statements	92.05%	green
🟢 Functions	85.98%	green
🟢 Branches	88.64%	green

---

📊 View Detailed Coverage Report

ℹ️ Coverage Thresholds

• 🟢 Excellent (≥ 80%)
• 🟡 Good (60-79%)
• 🟠 Fair (40-59%)
• 🔴 Poor (< 40%)

[github-actions]

⚠️ OWASP Dependency Check - @dittolive/ditto-chat-core

Medium severity vulnerabilities detected

Severity	Count
🔴 Critical	0
🟠 High	0
🟡 Medium	1
🔵 Low	0
Total	1

📋 Vulnerability Details

• CVE-2025-64718 (MEDIUM) in js-yaml:3.14.2
  • Description: js-yaml is a JavaScript YAML parser and dumper. In js-yaml 4.1.0 and below, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution ( proto ). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1. Users can protect against this kind of attack on the server by using node --disable-proto=delete or deno (in Deno, pollution protection is on by default).
  • CVSS: 5.3

---

📊 View Full HTML Report

ℹ️ How to fix vulnerabilities

1. Update vulnerable dependencies to patched versions
2. Run npm audit fix or npm audit fix --force in the root directory
3. Check for alternative packages if updates aren't available
4. Review and update your package.json and package-lock.json

[github-actions]

⚠️ OWASP Dependency Check - @dittolive/ditto-chat-ui

Medium severity vulnerabilities detected

Severity	Count
🔴 Critical	0
🟠 High	0
🟡 Medium	1
🔵 Low	0
Total	1

📋 Vulnerability Details

• CVE-2025-64718 (MEDIUM) in js-yaml:3.14.2
  • Description: js-yaml is a JavaScript YAML parser and dumper. In js-yaml 4.1.0 and below, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution ( proto ). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1. Users can protect against this kind of attack on the server by using node --disable-proto=delete or deno (in Deno, pollution protection is on by default).
  • CVSS: 5.3

---

📊 View Full HTML Report

ℹ️ How to fix vulnerabilities

1. Update vulnerable dependencies to patched versions
2. Run npm audit fix or npm audit fix --force in the root directory
3. Check for alternative packages if updates aren't available
4. Review and update your package.json and package-lock.json