[Snyk] Security upgrade fonttools from 4.38.0 to 4.43.0

[gkorland]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • benchmark/requirements.txt

⚠️ Warning

botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5	XML External Entity (XXE) Injection SNYK-PYTHON-FONTTOOLS-6133203	fonttools: 4.38.0 -> 4.43.0	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 XML External Entity (XXE) Injection

Summary by CodeRabbit

• New Features

  • Introduced a new dependency to enhance security and avoid vulnerabilities.

• Documentation

  • Updated requirements documentation to reflect security improvements.

[coderabbitai]

Walkthrough

The recent update in the codebase introduces a new dependency, fonttools, specified in the requirements.txt file. This addition is not a direct requirement for the project's functionality but serves as a security measure to mitigate a known vulnerability. No changes to the public API or exported entities were made.

Changes

File Path	Change Summary
benchmark/requirements.txt	Added fonttools>=4.43.0 as a comment for security reasons.

🐇✨
To keep our code so spry and quick,
A font tool joins the mix, not a trick.
No bugs to chase, no flaws to fix,
Just a rabbit coder's security pick. 🛡️🥕

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ?

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• You can reply to a review comment made by CodeRabbit.
• You can tag CodeRabbit on specific lines of code or files in the PR by tagging @coderabbitai in a comment.
• You can tag @coderabbitai in a PR comment and ask one-off questions about the PR and the codebase. Use quoted replies to pass the context for follow-up questions.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between eeb01bc and baa3fc6.

Files selected for processing (1)

• benchmark/requirements.txt (1 hunks)

Files skipped from review due to trivial changes (1)

• benchmark/requirements.txt