chore(deps): Fix vulnerabilities

[son-oz]

Summary

Testing Process

Checklist

• Add a reference to related issues in the PR description.
• Add unit tests if applicable.
• Add integration tests if applicable.
• Add property-based tests if applicable.
• Update documentation if applicable.

Note

If you are using Monitor in your stack, consider adding your team or organization to our list of Monitor Users in the Wild!

Summary by CodeRabbit

• Chores
  • Updated vulnerability scanner configuration to ignore additional known security advisories, extending the list of ignored entries for better build process management.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The pull request adds two new ignored vulnerability entries (RUSTSEC-2025-0119 and RUSTSEC-2025-0134) to the osv-scanner configuration file, extending the list of vulnerabilities that the scanner will ignore during execution.

Changes

Cohort / File(s)	Summary
Configuration Updates osv-scanner.toml	Added two new vulnerability ignore entries to the [[IgnoredVulns]] section: RUSTSEC-2025-0119 and RUSTSEC-2025-0134, each with associated rationale metadata

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop, hop, rusty vulns away,
Two new rules for safety's way,
The scanner now will gently skip,
What once might've caused a trip,
Configuration keeps us bright! ✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description contains only template structure with empty Summary and Testing Process sections; no actual details about the changes, rationale, or vulnerabilities being ignored are provided.	Fill in the Summary section with details about which vulnerabilities are being ignored and why, and document any testing performed in the Testing Process section.
Title check	❓ Inconclusive	The title mentions fixing vulnerabilities but provides no specifics about which vulnerabilities or configuration changes are being made.	Consider using a more specific title like 'chore: Ignore RUSTSEC-2025-0119 and RUSTSEC-2025-0134 vulnerabilities' to better communicate the actual change.

✅ 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.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-vulnerabilities

---

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