EXTENSIONS

One workflow, `@dataverket/mirror-forgejo-to-github`, that mirrors every repository of a Forgejo org to a GitHub org and keeps it that way.

One workflow, `@dataverket/platform-health`, that checks the forges, S3 gateways and HTTP endpoints a repository names and fails when one of them is down.

Forgejo (or Gitea) administration for swamp over the /api/v1 REST API with a scoped access token, in one model type, `@dataverket/forgejo`.

Drive pull requests on a Forgejo or Gitea forge: list and read them,

Record Forgejo or Gitea repository stars and counters over time.

Record a Forgejo or Gitea branch's commits and head over time.

Record Forgejo or Gitea issues and how many stay open over time.

Record Forgejo or Gitea releases and their asset downloads.

Code-reading methods for @shrug/forgejo — map a repository's file tree, read individual files, and snapshot every matching text file into one reviewable data blob. Turns a metadata-only forge node into a source for code review and IaC analysis.

Administration of a Forgejo (or Gitea) server over its /api/v1 REST API, authenticated with a scoped access token. Find or create organizations and repositories and update their settings; run GitHub pull-mirrors (create via /repos/migrate, reconcile interval, visibility and description, queue immediate syncs); audit every mirror's sync health; manage pull requests (open, inspect mergeability and head CI state, merge); and audit or repoint repository webhooks so a hook pointing at an old CI target is reported. Changes are find-or-create or reversible (archive/unarchive), except the guarded pr_merge. There are no delete methods: an empty repository left by a failed migration is reported, not deleted. Secrets are never output: mirror source credentials are write-only, and webhook operations neither read nor write the hook secret.

Drive [Forgejo](https://forgejo.org/) and [Gitea](https://gitea.io/) instances