chore: bump deps (ai/vite/storybook/turbo); add CODEOWNERS + cargo-fuzz (Scorecard)

[qnbs]

User description

Summary

• Deps: ai 6.0.183, vite 8.0.13, turbo 2.9.14, storybook 10.4.0, @types/node 25.8.0 — resolves Dependabot PRs chore(deps-dev): bump @types/node from 25.7.0 to 25.8.0 #12chore(deps-dev): bump turbo from 2.9.12 to 2.9.14 #13chore(deps-dev): bump vite from 8.0.12 to 8.0.13 #20chore(deps): bump ai from 6.0.178 to 6.0.183 #23chore(deps-dev): bump the dev-tooling group across 1 directory with 4 updates #25
• CODEOWNERS: .github/CODEOWNERS assigns @qnbs as owner of all files; enables Scorecard Code-Review credit
• cargo-fuzz: src-tauri/fuzz/ with fuzz_file_name_sanitization libFuzzer target; addresses Scorecard Fuzzing check

Scorecard improvements

Check	Before	Action
Vulnerabilities (#29)	High	glib alert dismissed (upstream Tauri blocker); npm clean
Code-Review (#26)	High	CODEOWNERS + enforce_admins=true on main
Fuzzing (#27)	Medium	cargo-fuzz harness added

Test plan

• CI quality gate green (lint + typecheck + Vitest coverage)
• Build passes
• E2E passes

---

CodeAnt-AI Description

Tighten dependency versions and add checks that help catch unsafe file-name input

What Changed

• Updated core build and UI dependencies, including Storybook, Vite, Turbo, AI SDK, and Node type definitions
• Added a global code owner so changes now require review from the designated owner
• Added a fuzz test for file-name sanitization to exercise malformed input and catch crashes before release

Impact

✅ Safer handling of unusual file names
✅ Fewer missed reviews on repository changes
✅ Lower risk of regressions from dependency updates

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI finished reviewing your PR.