pkg.soopen package index

brew

Install forgejo-runner with Homebrew

Package metadata for forgejo-runner, from local pkg.so sources. Version 13.2.1 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install forgejo-runner

local Homebrew formula metadata

overview

Package summary

Package metadata for forgejo-runner, from local pkg.so sources.

Commands and aliases

No executable aliases were found in the local package database.

history

Project history and usage

Forgejo Runner is the official worker program for Forgejo Actions continuous integration.

Project history

Forgejo Runner is maintained as the execution service for Forgejo Actions. Forgejo schedules workflows, while separately installed runners fetch and execute their jobs.

Adoption history

Forgejo documents binary, container, and distribution-package installation routes. These establish supported deployment channels without quantifying adoption.

How it is used

Register the runner, configure execution labels, and start its daemon with an explicit configuration path. Labels select container-based or direct host execution.

Why package nerds care

Its separate installation lets administrators manage workflow execution infrastructure independently of the forge server.

Timeline

  • Forgejo 1.21: Actions became enabled by default in Forgejo.

Related projects

  • Forgejo; Docker; Podman; LXC.

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for forgejo-runner. Package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Formula metadata declares a service or daemon block.
  • Homebrew bottle metadata is available for 5 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux
/home/runner/runner-config.yml

Credential files

Credential-bearing paths to review before unattended agent runs.

Linux
/home/runner/runner-config.yml

executables

Installed executables

CommandKindExposureNote
No executable data was present.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-11-04
manager version13.2.1
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://code.forgejo.org/forgejo/runner

install metadata

Package metadata

Package keybrew:forgejo-runner
Version13.2.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/forgejo-runner
Homepagehttps://code.forgejo.org/forgejo/runner
Upstream docshttps://code.forgejo.org/forgejo/runner
LicenseGPL-3.0-or-later
Source archivehttps://code.forgejo.org/forgejo/runner/archive/v13.2.1.tar.gz
Build dependenciesgo
Bottleavailable (on arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux)
Homebrew post-installnot defined
Servicedeclared
CaveatsConfig file: $HOMEBREW_PREFIX/etc/forgejo-runner/config.yaml

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameforgejo-runner
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment