Skip to content

fix(deps): raise torch-server development floors past known advisories - #111

Merged
MrScripty merged 2 commits into
mainfrom
deps/scan-findings-harness-and-dev-floors
Nov 6, 2026
Merged

MrScripty merged 2 commits into
mainfrom
deps/scan-findings-harness-and-dev-floors

Conversation

@MrScripty

@MrScripty MrScripty commented Nov 6, 2026 •

Copy link
Copy Markdown
Owner

Summary

Scorecard's OSV scan reads each >= bound in torch-server/requirements.txt as the installed version. So torch>=2.1.0 alone reported 23 advisories in the "Vulnerabilities" alert, and transformers, fastapi and accelerate reported 6 more.

This PR raises those floors past the known advisories:

Package Was Now
torch ≥ 2.1.0 ≥ 2.13.0
transformers ≥ 4.36.0 ≥ 4.55.0
fastapi ≥ 0.104.0 ≥ 0.109.1
accelerate ≥ 0.25.0 ≥ 1.15.0

The file is still an unpinned, direct-development input that managed installs never read. A fresh pip install already resolves above all of these, so the change only rules out old vulnerable versions. docs/SECURITY.md notes why the floors sit where they do.

The interop harness lock was in an earlier revision of this PR. I dropped it because #110 regenerates that lock against a patched Pantograph pin.

Verification

I checked every PyPI advisory in the latest Scorecard Vulnerabilities result against its OSV ranges. None affects the new floors: each one is fixed at or below the new floor, or its last affected version is below it.

🤖 Generated with Claude Code

…oors

The Pantograph guard interop harness lock was stale: Pumas's own
dependencies moved after it was generated, so the documented
`--offline --locked` run failed before compiling. Re-resolve it
minimally and move tokio, zstd, zstd-safe, zstd-sys, h2,
crossbeam-epoch and anyhow to the patched versions rust/Cargo.lock
already uses. zip 2.4.2 and pyo3 0.23.5 remain because the pinned
Pantograph commit requires zip "2" and pyo3 "0.23"; SECURITY.md
records why.

Scorecard reads each lower bound in torch-server/requirements.txt as
the installed version, so torch>=2.1.0 alone reported 22 advisories.
Raise the torch, transformers, fastapi and accelerate floors past
their known advisories. The file stays a direct-development input.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: cd46a97c-94fd-401a-baa9-a3e7be1f153f
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

#110 repins the harness to a Pantograph commit with patched zip and
pyo3 and regenerates the same lock, so keep this change to the
torch-server development floors.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MrScripty MrScripty changed the title fix(deps): clear scan findings in the interop harness lock and dev floors fix(deps): raise torch-server development floors past known advisories Nov 6, 2026
@greptile-apps

greptile-apps Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The PR appears safe to merge; no actionable regression was found.

Summary

Updates development dependency floors and refreshes the standalone Pantograph test harness lock.

  • The Pantograph test harness now uses a refreshed Rust dependency lock.
  • Torch sidecar development installs now require higher minimum versions for four packages.

No actionable issues were found. MrScripty explicitly defers the remaining zip and pyo3 updates because Pantograph’s pinned requirements exclude patched versions.

Reviews (1) · Last reviewed commit: "fix(deps): clear scan findings in the in..." · Reviewed by Greptile

@MrScripty
MrScripty merged commit 0a4c0a8 into main Nov 6, 2026
59 of 60 checks passed
@MrScripty
MrScripty deleted the deps/scan-findings-harness-and-dev-floors branch November 6, 2026 18:37
MrScripty added a commit that referenced this pull request Nov 6, 2026
The audit remediation landed under [Unreleased], but it ships in the
untagged 0.8.0. Merge it into the 0.8.0 section, correct the stale
dependency line (Vite 8.3.5, zip is 9.4 not 2.6.1, rusqlite 0.41), and
note the shared desktop contract package and the test-harness advisory
repins. The release notes gain the desktop/runtime hardening, the Rust
API removals and Result signatures, the HTTPS-first plaintext sources,
and a pointer to the moved-download recovery steps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant