Repo brief: TwiN/gatus

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T23:51:21.517Z · commit 4d15cb7eed62

Verdict

Healthy — Healthy across all four use cases

• Last commit 4d ago
• 32+ active contributors
• Distributed ownership (top contributor 37% of recent commits)
• Apache-2.0 licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Gatus is a developer-oriented automated status page and health dashboard written in Go that monitors services using HTTP, ICMP, TCP, and DNS queries. It evaluates health checks against user-defined conditions (status code, response time, certificate expiration, body content) and triggers alerts via 25+ integrations (Slack, Teams, PagerDuty, Discord, Twilio, email, GitHub, GitLab, Datadog, AWS SES, and more). It provides both a web UI and incident support with a focus on Kubernetes deployments. Modular monolith structure: core health-check logic in the root with alerting/ subdirectory containing 25+ provider integrations (each provider is a standalone package like…

Start here

Open these first:

• alerting/config.go — Core alerting configuration parser that ties all 30+ alert provider implementations together through a unified interface.
• alerting/provider/provider.go — Provider interface definition that all alert backends (Slack, Teams, PagerDuty, etc.) must implement; critical abstraction…
• alerting/alert/alert.go — Alert execution logic that orchestrates status checks, condition evaluation, and provider dispatch during incidents.
• Dockerfile — Container build definition establishing the runtime environment and deployment model for the status page service.
• Makefile — Build automation and development workflow entry point that defines how tests, binaries, and containers are created.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/TwiN/gatus.git
cd gatus
go mod download
make build  # inferred from Makefile presence
go run . # or docker run -p 8080:8080 ghcr.io/twin/gatus:stable

Daily commands:

From README: docker run -p 8080:8080 ghcr.io/twin/gatus:stable or docker run -p 8080:8080 twinproduction/gatus:stable. For local dev (inferred from Makefile): go run . -config config.yaml (requires creating a YAML…

…shortened for this brief.

Key cautions & unknowns

• Provider-specific secrets: Each alerting provider requires different env vars or config fields (AWS credentials for SES, Discord webhook URLs, GitHub tokens, etc.); misconfiguration silently disables that provider…
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.