fix: remediate security insights#325
Conversation
|
Warning Review limit reached
Next review available in: 56 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (14)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
5b5e033 to
8a50906
Compare
Gavel summary
Totals: 424 passed · 0 failed · 3 skipped · 12.9s |
cb5a119 to
caaa049
Compare
Update vulnerable Go dependencies in the root module and hx command, including OpenTelemetry, go-jose, x/crypto, x/net, and xz, so govulncheck reports no findings. Redact sensitive HTTP headers in curl trace output, enforce redaction at the Tracef boundary, avoid over-redacting non-secret trace fields, and remove deterministic hashes from long-secret redaction output. Tighten GitHub workflow token permissions, run Scorecard on master, update the Scorecard action, and keep CI stable by avoiding duplicated gavel linting and external httpbin header tests.
caaa049 to
e5e545d
Compare
Faro reported high severity security insights for commons across Dependabot, CodeQL, and OpenSSF Scorecard.
This updates vulnerable Go deps in root and cmd/hx modules, redacts sensitive headers in curl trace output, enforces trace log redaction, and removes deterministic fingerprints from long-secret redaction output.
Workflow tokens are restricted to read-by-default, Scorecard now runs on master, and the Scorecard action is updated.
Branch-Protection, Code-Review, and Signed-Releases require GitHub repository settings / release policy changes outside this PR.