readystack/gitea repository overview

⁠Gitea

readystack/gitea:v28.3.0-CE-ubuntu24.04-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/gitea/recipe⁠
• Upstream source at this release's pinned commit (v28.3.0): https://github.com/go-gitea/gitea/tree/4f5a3e13e5f3aca85d830e3a9024c893b0bbf1e1⁠
• Product page: https://readystack.dev/products/gitea⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/gitea⁠
• Release history (JSON): https://readystack.dev/api/releases/gitea⁠
• Defect record: https://readystack.dev/defects.html?product=gitea⁠
• Today's scan: https://readystack.dev/products/gitea#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=gitea⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of Gitea v28.3.0, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Development teams who want a self-hosted Git service with code review, issues and CI/CD in one place.

Why: Gitea is a self-hosted, all-in-one software development service: Git hosting, code review, issue tracking, project boards, a wiki, a package registry and CI/CD in one application.

Use case: A company must keep its source code on its own servers. Gitea gives its developers repositories, pull requests with code review, issues and a wiki on one internal server, and its built-in CI/CD builds and tests each change there too.

About the upstream project, written from its own description: https://github.com/go-gitea/gitea⁠ · https://docs.gitea.com/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:f6bdd508ee992253c897f1f4768c206745c88f0357bdb9432553c99f81713e0e on 2026-11-10.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v2, ce.rodeo's current rubric; scans before 2026-11-08 used cerodeo-v1) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/gitea⁠
• ReadyStack release check — passed at release on 2026-11-09: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:f6bdd508ee992253c897f1f4768c206745c88f0357bdb9432553c99f81713e0e; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/gitea:v28.3.0-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (gitea).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v28.3.0-CE-ubuntu24.04-r1 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/gitea:v28.3.0-CE-ubuntu24.04-r1

# ✗ unsupported (do not pull)
docker pull readystack/gitea:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/gitea:v28.3.0-CE-ubuntu24.04-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

SINGLE self-contained container. The gitea Go binary runs with an EMBEDDED sqlite database — no external Postgres/MySQL. The image IS the complete running instance. Web UI + Git over HTTP on :3000; Git over SSH on :2222, served by Gitea's built-in SSH server (the image has no sshd).

docker run -d --name gitea -p 3000:3000 -p 2222:2222 -v gitea-data:/data readystack/gitea:v28.3.0-CE-ubuntu24.04-r1

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/gitea⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:b80d6c7290be1e9121d9b818660d8f4083fbed6788caa92d1adb322bbc0c2993 on 2026-11-09.

— ReadyStack · readystack.dev