Skip to content

chore: bump detect-agent to 0.6.0 - #522

Merged
blainekasten merged 2 commits into
mainfrom
cursor/update-detect-agent-0.6.0-cde0
Aug 12, 2026
Merged

chore: bump detect-agent to 0.6.0#522
blainekasten merged 2 commits into
mainfrom
cursor/update-detect-agent-0.6.0-cde0

Conversation

@blainekasten

Copy link
Copy Markdown
Collaborator

Summary

Bumps detect-agent from >=0.5.0 to >=0.6.0 and refreshes lockfiles.

Why

Follow-up to detect_agent 0.6.0 — agent detection updates for claude, codex, gemini, opencode, kimi code, and grok (detect_agent#17).

Requested on the release PR: togethercomputer/detect_agent#18

Changes

  • pyproject.toml: detect-agent>=0.6.0
  • uv.lock / requirements-dev.lock: pin detect-agent==0.6.0

No call-site changes needed — determine_agent() return shape (is_agent / agent.name) is unchanged.

Test plan

  • uv sync --all-extras installs detect-agent==0.6.0
  • Smoke: determine_agent() / agent_headers()
  • pytest tests/test_client.py -k "header or agent or user_agent" (52 passed)

Update together-py to the latest detect-agent release for improved
agent detection (claude, codex, gemini, opencode, kimi code, grok).

Co-authored-by: Blaine Kasten <blainekasten@gmail.com>
@broly-code-security-scanner

broly-code-security-scanner Bot commented Aug 12, 2026

Copy link
Copy Markdown

Broly Security Scan

Note

Summary

5 actionable finding(s) in this PR

  • 🟡 5 medium

All actionable items are in the table below.

No finding is at or above high, so this check is not blocking. The findings above are still tracked and reported.

Severity Scanner Issue Location Dismiss Verdict
🟡 MEDIUM SCA aiohttp@3.13.3 — 48 vulnerabilities (worst:
GHSA-2fqr-mr3j-6wp8)
→ >= 3.14.3
uv.lock:1 d1 🔺 TRUE_POSITIVE · Confidence: HIGH
🟡 MEDIUM SCA pygments@2.19.2 — 2 vulnerabilities (worst:
GHSA-5239-wwwm-4pmq)
→ >= 2.20.0
uv.lock:1 d4 🔺 TRUE_POSITIVE · Confidence: HIGH
🟡 MEDIUM SCA idna@3.11 — 2 vulnerabilities (worst:
GHSA-65pc-fj4g-8rjx)
→ >= 3.15
uv.lock:1 d2 🔺 TRUE_POSITIVE · Confidence: HIGH
🟡 MEDIUM SCA pytest@9.0.2 — 2 vulnerabilities (worst:
GHSA-6w46-j5rx-g56g)
→ >= 9.0.3
uv.lock:1 d5 🔺 TRUE_POSITIVE · Confidence: HIGH
🟡 MEDIUM SCA urllib3@2.6.3 — 4 vulnerabilities (worst:
GHSA-mf9v-mfxr-j63j)
→ >= 2.7.0
uv.lock:1 d6 🔺 TRUE_POSITIVE · Confidence: HIGH

Dismiss false positives

Tick a box to dismiss the finding; untick it to bring the finding back. That is the same as replying /broly dismiss d1 and /broly undismiss d1. To record why it is a false positive, reply with /broly dismiss d1: your reason instead — Broly reuses those reasons to triage similar findings across the org.

  • d1 · 🟡 MEDIUM   · uv.lock:1 · aiohttp@3.13.3 — 48 vulnerabilities (worst: GHSA-2fqr-mr3j-6wp8)
  • d2 · 🟡 MEDIUM   · uv.lock:1 · idna@3.11 — 2 vulnerabilities (worst: GHSA-65pc-fj4g-8rjx)
  • d4 · 🟡 MEDIUM   · uv.lock:1 · pygments@2.19.2 — 2 vulnerabilities (worst: GHSA-5239-wwwm-4pmq)
  • d5 · 🟡 MEDIUM   · uv.lock:1 · pytest@9.0.2 — 2 vulnerabilities (worst: GHSA-6w46-j5rx-g56g)
  • d6 · 🟡 MEDIUM   · uv.lock:1 · urllib3@2.6.3 — 4 vulnerabilities (worst: GHSA-mf9v-mfxr-j63j)

Note

Re-scan this PR anytime with /broly scan — useful after /broly undismiss, or to refresh findings without a new push.

Broly — SAST (zai-org/GLM-5.2) · Secrets · SCA · IaC · GH Actions · Base Images · Supply Chain Threats · Exploit Chains · Adversarial Verification

We're continuously improving Broly's accuracy and finding quality — your feedback is valuable. False positives, missed findings, bugs, and feature requests all welcome.

Ask in #security-engineering   Powered by Together AI

@blainekasten
blainekasten merged commit abb6f5d into main Aug 12, 2026
12 checks passed
@github-actions github-actions Bot mentioned this pull request Aug 12, 2026
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.

3 participants