Fix uv audit vulnerabilities

[vinitkumar]

Summary by Sourcery

Address dependency security vulnerabilities and document the project’s dependency management approach.

Bug Fixes:

• Raise the minimum urllib3 version and align lockfiles/requirements to avoid known security vulnerabilities.
• Pin Pygments as a development dependency at a secure minimum version to mitigate reported issues.

Enhancements:

• Keep runtime, lockfile, and legacy requirements inputs in sync for both uv- and requirements-based workflows.

Documentation:

• Document the project’s dependency security strategy, including dependency floors, lockfiles, and alignment between uv and requirements-based installs.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Aligns dependency security posture by raising floors for vulnerable packages and synchronizing pyproject, legacy requirements files, and uv.lock so uv audit passes and all resolvers agree.

File-Level Changes

Change	Details	Files
Raise minimum versions for vulnerable runtime and dev dependencies and document the dependency security model.	Set a minimum version floor for urllib3 to avoid known vulnerabilities. Set a minimum version floor for pygments in development dependencies. Explain how runtime dependencies, lockfiles, and legacy requirements inputs are kept in sync for security fixes.	pyproject.toml lat.md/architecture.md
Synchronize requirements inputs and the uv lockfile with the new secure dependency floors.	Update requirements.in and requirements-dev.in to match the new dependency minimums. Regenerate or update requirements.txt and requirements-dev.txt from the .in files. Refresh uv.lock so uv audit sees the updated, non-vulnerable dependency graph.	requirements.in requirements-dev.in requirements.txt requirements-dev.txt uv.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.56%. Comparing base (877c873) to head (a135217).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #295   +/-   ##
=======================================
  Coverage   98.56%   98.56%           
=======================================
  Files           6        6           
  Lines         487      487           
=======================================
  Hits          480      480           
  Misses          7        7           

Flag	Coverage Δ
unittests	98.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.