ReleaseBar is a release-freshness dashboard for public GitHub users and organizations. It combines releases, unreleased commits, repository activity, CI, and open work so maintainers can see which projects need attention.
The public service runs at release.bar, with no installation required.
To run the source locally:
git clone https://github.com/steipete/ReleaseBar.git
cd ReleaseBar
npm ciReleaseBar requires Node.js 22.12 or newer. Node.js 24 is the version used by CI.
Open a dashboard for any public GitHub owner, such as release.bar/steipete, or read the same cached data from the API:
curl -fsSL https://release.bar/api/steipete \
| jq '{owners: [.owners[].login], repositories: (.projects | length), cache: .cache.state}'The response may initially report partial or stale while deeper release and CI data hydrates in the background.
| Route | Shows |
|---|---|
/ |
Recently requested public dashboards |
/:owner |
Release health for one GitHub user or organization |
/:owner/activity |
Day, week, or month public activity grouped by repository |
/:owner/:repo |
Release cadence, contributors, languages, churn, open work, and recent audience signals |
Dashboard settings can add public owners, organizations, or explicit repositories to the current URL. Query parameters cover shareable filters such as forks=true, archived=true, unreleased=false, owners=openclaw,steipete, and repos=owner/name.
See the product guide for login, GitHub App, filtering, attention, trust, and repository-detail behavior.
Owner dashboards return lightweight public repository metadata first, then hydrate release, commit, pull-request, and CI data in bounded background batches. Cached data remains visible during GitHub outages or rate limits, and each payload reports whether its data is fresh, stale, partial, warming, or errored.
ReleaseBar ignores private repositories even when a GitHub App installation includes them. Installing the app supplies dedicated GitHub API quota for covered public sources; it does not turn ReleaseBar into a private-repository browser or a GitHub write proxy.
The Worker exposes cached public endpoints for owner dashboards, activity, repository details, audience signals, and public GitHub profile context. Swagger-compatible OpenAPI 3.1 is available at /openapi.json.
See the public API reference for response shapes, cache semantics, and agent guidance. The refresh scheduler describes background hydration, retries, quota selection, and webhook-driven refreshes.
Static builds use releasebar.config.json; the hosted service serves arbitrary public owner routes through the Cloudflare Worker API. See Self-hosting and operations for configuration, local Worker modes, GitHub App setup, optional AI summaries, Cloudflare bindings, and deployment checks.
npm ci
npm run check:static
npm run devThe Vite development server runs on http://127.0.0.1:5173. Run npm run dev:worker alongside it when testing Worker API routes locally.
Product direction and boundaries live in VISION.md.
MIT. See LICENSE.
