dimmas893/github-runner-single resource
None observed · 2026-08-28
Health v2 · maintenance only
22/100
- Activity 0
- Release rhythm 35
- Longevity 49
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 690
- days_rel: n/a
- days_push: 690
- n_releases_24m: 0
Adoption not part of the score
1939 stars · 1697 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A Dockerfile-based project that packages a single self-hosted GitHub Actions runner in a container. It lets users spin up a disposable CI runner instance for their GitHub repositories.
Use cases
- run a self-hosted github actions runner in docker
- spin up a disposable CI runner container
- set up a github runner on my own server
- containerize a github actions runner
- run CI jobs outside github-hosted runners
When to choose
- you need a self-hosted GitHub Actions runner deployed via Docker
- you want an isolated, single-instance runner environment
- you need CI jobs to run on your own hardware or network
When to avoid
- you only need GitHub-hosted runners
- you require autoscaling fleets of runners rather than a single instance
- you don't use GitHub Actions for CI
Facets
infra-config · maturity active
deployment ci-cd container-runtime developer-tools developer-tools self-hosted github-actions self-hosted-runner dockerfile ci-runner devops automation containers docker linux
1 source
- readme: https://github.com/dimmas893/github-runner-single · fetched 2026-08-28 · a93d87fef7a9
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| dimmas893/github-runner-single | main | 22 |
For agents
markdown · JSON · MCP: product_card(name="dimmas893/github-runner-single")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem