Skip to content

docs: add Fuzzing status badge to README#23

Merged
askalf merged 1 commit into
masterfrom
docs/fuzzing-badge
Jul 12, 2026
Merged

docs: add Fuzzing status badge to README#23
askalf merged 1 commit into
masterfrom
docs/fuzzing-badge

Conversation

@askalf

@askalf askalf commented Jul 12, 2026

Copy link
Copy Markdown
Owner

Adds the ClusterFuzzLite (cflite.yml) status badge next to CI/CodeQL/Scorecard. Docs-only.

Also the live confirmation of the new required-approval gate: this PR should be blocked until the reviewer bot approves it.

Completes the security-signals badge row (CI · CodeQL · Fuzzing · OpenSSF
Scorecard) with the ClusterFuzzLite workflow status. Docs-only.

@sprayberry-reviewer sprayberry-reviewer left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review from the Sprayberry Labs fleet code reviewer.

Verdict: no blocking issues found — approving.


What I checked

The change is exactly one line added to README.md:

[![Fuzzing](https://github.com/askalf/agent-security-stack/actions/workflows/cflite.yml/badge.svg)](https://github.com/askalf/agent-security-stack/actions/workflows/cflite.yml)
  1. Workflow file exists — confirmed cflite.yml is present in .github/workflows/ via the GitHub contents API. The badge won't show a broken link or a perpetual "no status" state.
  2. URL pattern is correct — matches the existing CI and CodeQL badge URLs exactly (…/workflows/<name>.yml/badge.svg → link to …/workflows/<name>.yml).
  3. Repo is public — the badge will render for all viewers; no visibility gap.
  4. Placement is coherent — inserted between CodeQL and OpenSSF Scorecard, consistent with CI/security badge grouping.

No logic, no code, no tests — nothing to introduce a correctness bug, security hole, or missing coverage.

@askalf askalf merged commit 028335f into master Jul 12, 2026
3 checks passed
@askalf askalf deleted the docs/fuzzing-badge branch July 12, 2026 17: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.

2 participants