Buildfjord is a GitHub Actions dashboard built to make repository health visible without drowning you in tooling overhead.
It gives you a focused board for the repositories that matter right now, keeps live pipeline signal front and center, and uses a safer server-managed session flow instead of exposing GitHub tokens to browser storage.
If you want a simple way to watch builds across a handful of repositories, this is the point of the project.
- Focused workflow signal instead of a generic CI dashboard
- GitHub OAuth app flow with server-managed sessions
- Local-first development with a clean path toward public deployment
- Live workflow updates, recent run context, and fast failure visibility
- CI, security checks, tests, and repo hygiene already in place
- GitHub OAuth sign-in
- Server-managed session cookie for GitHub access
- Searchable repository picker modal
- Tracked repository cards ordered by recent run activity
- Live status streaming for active workflows
- Recent runs per repository
- Failure alerts plus a
Needs attentionsummary - Responsive layout with desktop and mobile support
Getting Buildfjord running locally is straightforward:
Use this callback URL for local development:
http://localhost:3000/api/auth/github/callbackYou can create the app in GitHub Developer Settings.
Copy the example file:
cp .env.example .env.localThen add your real GitHub OAuth credentials to .env.local:
GITHUB_CLIENT_ID=your_real_client_id
GITHUB_CLIENT_SECRET=your_real_client_secretnpm install
npm run devOpen http://localhost:3000.
Buildfjord will send you through the GitHub OAuth flow and create a server-managed session when you come back.
npm run dev
npm run lint
npm run test
npm run test:watch
npm run security:check
npm run ci:check
npm run buildBuildfjord includes:
- GitHub Actions CI for lint, test, and build
npm auditenforcement throughnpm run security:check- Dependabot configuration for npm and GitHub Actions updates
src/componentsfor UI componentssrc/app/apifor auth and GitHub API routessrc/libfor domain helpers and server session handlingpublicfor repo and product assets.githubfor CI and repository automation
Buildfjord is ready for local use and early deployment:
- MIT licensed
- contributor docs and templates added
- server-side session handling in place
- baseline UI and domain tests in place
The main infrastructure limitation today is the local file-backed session store. It works well for one instance, but it should be replaced with a shared session backend before you run multiple instances.
- The GitHub OAuth app is only needed once per local setup
- The callback URL must match exactly
- Your tracked repository list stays in browser storage for convenience
- Your GitHub token stays on the server side after login
See CONTRIBUTING.md.
See SECURITY.md.
MIT. See LICENSE.
