Repository navigation
Fix filelock security pins and refresh agent documentation - #14
Merged
Merged
Conversation
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.
The public agent guide lacked Beta.5 mission, project, proof and Homebrew guidance and described private-checkout push restrictions as if they applied to every public clone. Document the actual boundaries and update workflow, require Homebrew 7+, and distinguish current source from immutable signed releases.
A fresh four-lock OSV scan also found three advisories in transitive filelock 3.32.5 (maximum CVSS 7.1). Add an explicit >=4.2.1 security floor and pin 4.2.4 with hashes. All other package versions remain unchanged. A regression verifies that the declared range and installed lock exclude the vulnerable versions; source test counters increase to 3356.
Validation: the new regression failed before remediation; targeted tests passed twice; full source and adversarial suites, native dependency smoke, pip consistency, public hygiene, site discovery, verifier-pin consistency and scoped Gitleaks passed. The fresh explicit scan of all four locks reports zero findings.
This updates source and documentation only. No release tag, signed Beta.5 archive, website deployment, Homebrew package or running operator installation is replaced. README and the unreleased changelog make this distinction explicit.