fix(strix): persist 1.5.3 reports and watch the hashed lock - #1047
Open
cursor[bot] wants to merge 1 commit into
Open
fix(strix): persist 1.5.3 reports and watch the hashed lock#1047cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
This was referenced Aug 16, 2026
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
marked this pull request as ready for review
August 16, 2026 23:21
seonghobae
force-pushed
the
cursor/bc-15a18b74-2e3f-4fc4-a777-0e75f221ff4a-38dd
branch
from
August 16, 2026 23:21
539f878 to
c134b0b
Compare
seonghobae
enabled auto-merge (squash)
August 16, 2026 23:21
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Required Strix on
strix-agent==1.0.4can finish a real scan, printPenetration 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.strix-agent==1.5.3(atomic CSV/MD writes; quit after scan).cryptography==50.0.0(CVE-2026-39892 floor + CVE-2026-69247 PKCS#7 timing-oracle fix).cryptography<49bound only at compile time viarequirements-strix-ci-overrides.txtand./scripts/ci/compile_strix_ci_lock.sh.pip install --require-hashes --no-deps.requirements-strix-ci.txtorrequirements-strix-ci-hashes.txtchanges.strix_runs/<run>/vulnerabilities/*.mdand still rejects console TUI lines.The missing-artifact rule is not weakened.
Next action
mainfirst. Required Strix ispull_request_target, so this lock cannot install until main's installer uses--no-depsand pip-audit uses--disable-pipon complete hashed locks.Closes #952.
Refs #961 and #969.