ci: harden repository gates and document audit - #10
Merged
Conversation
Add a static-analysis triage section to the security review covering the 309 open CodeQL alerts. All four critical `hard-coded-cryptographic-value` hits are `#[cfg(test)]` nonce fixtures; the cleartext-transmission hits on the retained upstream backend, feedback, and session-registry clients are unreachable because `REMOTE_SESSION_REGISTRY` forces `StorageMode::Local` and the product policy constants gate the remaining handlers. No alert is dismissed, so a later true positive stays visible. Document the pinned Rust/Node toolchain, the single supported package manager, the artifacts the project produces, the protected assets and generated files, and the repository-visibility rules in AGENTS.md. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
What
This pull request records the current security/code-review disposition and tightens two repository gates without changing product behavior.
Repository contract and CodeQL triage
AGENTS.md.CI and secret-scan hygiene
actions/checkoutuse from the pinnedv7.0.0SHA to the verifiedv7.0.1tag SHA. The patch includes Git argument escaping and pull-request safety fixes.gitleaks:allowannotations only to the three synthetic AWS/GitHub credential fixtures. Full-history fingerprints remain unchanged and real-secret detection is not relaxed.Verification
npm testnpm run verify:releasenpm pack --dry-run --jsoncargo fmt --all -- --checkcargo check -p chutes-build-core --lockedcargo test -p chutes-build-core --lockedcargo test -p xai-grok-tools --lib implementations::chutes:: --lockedgit diff --checkchutes-build 0.4.2 (f5fb363)The pull-request CI and CodeQL checks provide the authoritative cross-platform workflow validation.
Risk and compatibility
No public API, runtime behavior, dependency graph, package version, or artifact content changes. The only Rust edits are scanner annotations on test fixtures.
CHANGELOG.mdkeeps the changes underUnreleased; no new package, tag, release, or deployment is appropriate before review and merge.Known residual issues
lrualerts (GHSA-rhfx-m35p-ff5j) remain open. The fixed version is outside the ranges used byratatui 0.29and the current AWS SDK path; a broad Cargo dry-run would update 386 packages and introduces an MSRV 1.96 dependency above the repository's Rust 1.94.1 pin, so this requires a separately tested migration.mainrules.