This project now exposes a public SVG status badge from the deployed Cloudflare Worker:
https://grc-dashboard.jdeftekhari.workers.dev/badge?repo=OWNER/REPOhttps://grc-dashboard.jdeftekhari.workers.dev/badge/OWNER/REPO- Optional
?branch=BRANCH - Health probe:
https://grc-dashboard.jdeftekhari.workers.dev/health
Use standard Markdown in any README:
[](https://grc-dashboard.jdeftekhari.workers.dev/repo/shipstuff/GRC-Observability-Dashboard)For a non-default branch:
The worker reads the latest stored manifest for the repo and branch, then emits one of four states:
pass NN%warn NN%fail NN%not scanned
The score and color are derived from the existing compliance summary:
failif secrets were detected, critical vulnerabilities exist, or compliance is below 50%warnif high vulnerabilities exist, HTTPS is not enforced, security headers are incomplete, or compliance is below 80%passotherwise
GitHub’s "custom badge for your GitHub App" is not a dynamic URL. Per GitHub Docs, it is a static image you upload in the app settings, with a configurable background color.
Reference:
Operationally, that means:
- Register or edit the GitHub App in GitHub settings.
- Upload a static PNG/JPG/GIF logo under 1 MB.
- Set the badge background color in the app settings.
- Use the worker-hosted
/badgeendpoint separately for live per-repo observability status in READMEs or docs.
This split is intentional:
- GitHub App badge: branding for the app itself
- Worker badge endpoint: live compliance status for any scanned repo