Skip to content

fix(strix): persist 1.5.3 reports and watch the hashed lock - #1047

Open
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/bc-15a18b74-2e3f-4fc4-a777-0e75f221ff4a-38dd
Open

fix(strix): persist 1.5.3 reports and watch the hashed lock#1047
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/bc-15a18b74-2e3f-4fc4-a777-0e75f221ff4a-38dd

Conversation

@cursor

@cursor cursor Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Problem

Required Strix on strix-agent==1.0.4 can finish a real scan, print Penetration test completed, then exit before a durable report exists. The fail-closed gate (#891) then fails the required check even though the console already listed findings. That is a buyer-visible security-dashboard miss on every ruleset consumer.

A lock-only change also used to skip Strix quality CI, so the pin/override contract would not re-run when the install set changed.

Change

This is the landing successor to #961 (31dd4c94) plus the lock-watch and report-layout contract.

  • Pin strix-agent==1.5.3 (atomic CSV/MD writes; quit after scan).
  • Keep cryptography==50.0.0 (CVE-2026-39892 floor + CVE-2026-69247 PKCS#7 timing-oracle fix).
  • Resolve the stale cryptography<49 bound only at compile time via requirements-strix-ci-overrides.txt and ./scripts/ci/compile_strix_ci_lock.sh.
  • Install the complete hashed lock with pip install --require-hashes --no-deps.
  • Retrigger quality CI when requirements-strix-ci.txt or requirements-strix-ci-hashes.txt changes.
  • Prove the unchanged gate still requires strix_runs/<run>/vulnerabilities/*.md and still rejects console TUI lines.

The missing-artifact rule is not weakened.

Next action

  1. Land fix(strix): install hashed locks without pip re-resolution #969 on protected main first. Required Strix is pull_request_target, so this lock cannot install until main's installer uses --no-deps and pip-audit uses --disable-pip on complete hashed locks.
  2. Rebase this head onto that new main.
  3. Re-run exact-head install, import, CLI, quality, security, SBOM, and independent review.
  4. Merge only after current-head checks are green and a non-author approval exists. Do not self-approve. Do not merge fix(strix): persist 1.5.3 reports without dropping cryptography 50 #961 in parallel.

Closes #952.

Refs #961 and #969.

Open in Web View Automation 

Install the complete hashed lock with --no-deps and watch the compile
inputs so strix-agent 1.5.3 cannot drop the CVE-50 cryptography pin.
@seonghobae
seonghobae marked this pull request as ready for review August 16, 2026 23:21
@seonghobae
seonghobae force-pushed the cursor/bc-15a18b74-2e3f-4fc4-a777-0e75f221ff4a-38dd branch from 539f878 to c134b0b Compare August 16, 2026 23:21
@seonghobae
seonghobae self-requested a review as a code owner August 16, 2026 23:21
@seonghobae
seonghobae enabled auto-merge (squash) August 16, 2026 23:21
@cursor

cursor Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor Author

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@opencode-agent
opencode-agent Bot disabled auto-merge August 18, 2026 01:28
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.

strix-agent 1.0.4 crashes after producing a valid report, tripping the fail-closed gate; upgrade blocked by a cryptography CVE pin conflict

1 participant