Skip to content

chore: resolve the OpenSSF Scorecard alerts - #32

Merged
bakirgdev merged 1 commit into
mainfrom
chore/scorecard-alerts
Oct 17, 2026
Merged

bakirgdev merged 1 commit into
mainfrom
chore/scorecard-alerts

Conversation

@bakirgdev

Copy link
Copy Markdown
Owner

What and why

Resolves the six open OpenSSF Scorecard code-scanning alerts.

AI assistance: substantial

Verification

  • go vet ./... clean; env -u GOOS -u GOARCH go test -race ./... in crocmobile/: ok.
  • Each fuzz target run 20-30 s with go test -run=^$ -fuzz=^<Name>$: no failures (0.3-1.3 M execs each).
  • The two new FuzzRelayPorts seeds fail against the old check (seed#7, seed#8) and pass with the fix.
  • osv-scanner scan source -r --no-call-analysis=go . (2.7.0): both IDs filtered, "No issues found".
  • Matching scripts/verify-*.sh harness: not run, session.go unchanged.

Docs

  • Defect fixed or accepted: its docs/known-issues.md line deleted or added

Fuzzing: add Go native fuzz targets for relayPorts, validateThrottle,
proxyURL, classify and splitPaths. Fix the relayPorts range check, which
overflowed for huge BasePort or Transfers values and let them through
(or panicked in make); both extremes are now fuzz seeds.

Vulnerabilities: ignore GO-2026-5932 (x/crypto/openpgp, never imported)
and GHSA-vfj7-8cjw-p6xm (braces, build-time only), neither of which has
a fixed release, in osv-scanner.toml next to each manifest.

Record the four dismissed alerts in docs/known-issues.md.
@bakirgdev
bakirgdev merged commit f8f4c6b into main Oct 17, 2026
14 checks passed
@bakirgdev
bakirgdev deleted the chore/scorecard-alerts branch October 17, 2026 22:03
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.

1 participant