chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (in timezone Asia/Ho_Chi_Minh)

• Branch creation
  • "before 5am"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ⚠️ 9 package(s) with unknown licenses.

See the Details below.

License Issues

uv.lock

Package	Version	License	Issue Type
click	8.4.0	Null	Unknown License
filelock	3.29.0	Null	Unknown License
fsspec	2026.4.0	Null	Unknown License
hf-xet	1.5.0	Null	Unknown License
idna	3.16	Null	Unknown License
onnxruntime	1.26.0	Null	Unknown License
protobuf	7.35.0	Null	Unknown License
typer	0.25.1	Null	Unknown License
certifi	2026.5.20	Null	Unknown License

OpenSSF Scorecard

Scorecard details

Package	Version	Score	Details
pip/anyio	4.13.0	Unknown	Unknown
pip/certifi	2026.5.20	🟢 6.4	Details Check Score Reason Code-Review 🟢 5 Found 1/2 approved changesets -- score normalized to 5 Binary-Artifacts 🟢 10 no binaries found in the repo Maintained 🟢 8 8 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 8 Security-Policy 🟢 10 security policy file detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege Pinned-Dependencies 🟢 5 dependency not pinned by hash detected -- score normalized to 5 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Fuzzing ⚠️ 0 project is not fuzzed Signed-Releases ⚠️ -1 no releases found License 🟢 9 license file detected Branch-Protection ⚠️ 0 branch protection not enabled on development/release branches Packaging 🟢 10 packaging workflow detected SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0
pip/charset-normalizer	3.4.7	Unknown	Unknown
pip/click	8.4.0	Unknown	Unknown
pip/coverage	7.14.0	Unknown	Unknown
pip/filelock	3.29.0	Unknown	Unknown
pip/fsspec	2026.4.0	Unknown	Unknown
pip/hf-xet	1.5.0	Unknown	Unknown
pip/idna	3.16	Unknown	Unknown
pip/markdown-it-py	4.2.0	Unknown	Unknown
pip/onnxruntime	1.26.0	Unknown	Unknown
pip/packaging	26.2	Unknown	Unknown
pip/protobuf	7.35.0	Unknown	Unknown
pip/pygments	2.20.0	Unknown	Unknown
pip/rich	15.0.0	Unknown	Unknown
pip/tomli	2.4.1	Unknown	Unknown
pip/typer	0.25.1	Unknown	Unknown
pip/urllib3	2.7.0	Unknown	Unknown

Scanned Files

• uv.lock

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	onnxruntime@​1.24.4 ⏵ 1.26.0	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Potentially malicious package (AI signal): pypi pygments is 80.0% likely malicious Notes: This dependency fragment is security-unsafe: it contains multiple high-impact capabilities including dynamic eval-based code execution, OS command execution (backticks/IO.popen), sensitive local file disclosure (/etc/passwd and dictionary file processing), environment variable printing (possible secret leakage), and direct process termination driven by user-supplied PID. Unless the surrounding package guarantees these paths are never executed in production (e.g., test-only, unreachable, or removed), it should be treated as maliciously capable and rejected or tightly sandboxed. Confidence: 0.80 Severity: 0.95 From: uv.lock → pypi/pytest@9.0.3 → pypi/huggingface-hub@1.16.1 → pypi/pygments@2.20.0 ℹ Read more on: This package | This alert | What is AI-detected potential malware? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Given the AI system's identification of this package as malware, extreme caution is advised. It is recommended to avoid downloading or installing this package until the threat is confirmed or flagged as a false positive. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pygments@2.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report