Ignore CVE which does not apply to us

[ildyria]

We do not use JWT on golang side.

Summary by CodeRabbit

• Chores
  • Updated security scanning configuration to exclude a non-applicable vulnerability entry.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: afe64f27-3f35-4b1a-b3d1-56c532dc09c5

📥 Commits

Reviewing files that changed from the base of the PR and between adec05c and 16b429e.

📒 Files selected for processing (1)

• .trivyignore

---

📝 Walkthrough

Walkthrough

The .trivyignore configuration file was updated to add a new vulnerability entry (CVE-2026-34986) with a comment clarifying it does not apply since the project does not use JWT on the Go side. The existing CVE-2025-45769 entry remains unchanged, and a trailing newline was added to properly terminate the file.

Changes

Cohort / File(s)	Summary
Security Configuration .trivyignore	Added new CVE ignore entry (CVE-2026-34986) with explanatory comment regarding JWT non-usage on Go side, preserved existing entry, and normalized file line ending.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop through the trivyignore we go,
Adding CVE's that don't apply, you know,
JWT's not here on the FrankenPHP side,
So this vulnerability takes a stride,
Our security posture—cleaner, more bright! ✨

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}