RepoPilot

hyprwm/Hyprland

Hyprland is an independent, highly customizable, dynamic tiling Wayland compositor that doesn't sacrifice on its looks.

Healthy

Strong maintenance signals

MixedDependency

dependency CVE scan unavailable

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

dependency CVE scan unavailable

  • Concentrated ownership — top contributor handles 50% of recent commits
  • Last commit today
  • 30+ active contributors
  • BSD-3-Clause licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Informational only. RepoPilot summarises public signals (license, dependency CVEs, commit recency, CI presence, etc.) at the time of analysis. Signals can be incomplete or stale. Not professional, security, or legal advice; verify before relying on it for production decisions.

Repository brief

Repo brief: hyprwm/Hyprland

Generated by RepoPilot · document generated 2026-09-15 · concise human review Evidence snapshot · analyzed 2026-09-15T11:16:26.850Z · commit bd7f69536389

Verdict

Healthy — Strong maintenance signals

  • Last commit today
  • 30+ active contributors
  • BSD-3-Clause licensed
  • CI configured
  • 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Hyprland is a completely independent, GPU-accelerated dynamic tiling Wayland compositor written in C++ that provides a modern Linux desktop with advanced visual effects (gradient borders, blur, animations, shadows) without relying on wlroots, libweston, or other external compositor libraries. It solves the problem of wanting a highly customizable, visually polished tiling window manager on Wayland while maintaining bleeding-edge feature velocity and plugin extensibility. Monolithic C++ application compiled via CMake. Core logic resides in src/ (inferred from CMakeLists.txt), configuration examples in example/ (hyprland.lua, hyprland.desktop.in, layouts/), debug utilities in debug-tools/,…

Start here

Open these first:

  • CMakeLists.txt — Root build configuration defining all compilation targets, dependencies, and flags for the Wayland compositor—every…
  • hyprctl/src/main.cpp — Entry point for hyprctl IPC command interface; essential for understanding how external tools communicate with the…
  • hyprpm/src/main.cpp — Entry point for the plugin manager; critical for understanding plugin lifecycle, loading, and manifest handling.
  • hyprpm/src/core/PluginManager.hpp — Core plugin system abstraction; defines how plugins are discovered, loaded, and managed at runtime.
  • .clang-format — Code style definition enforced across the codebase; every contributor must adhere to this formatting standard.

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/hyprwm/Hyprland.git
cd Hyprland
make all  # or cmake-based build per Makefile
# Install following docs/install or example/hyprland.desktop.in

Detailed setup in docs/ISSUE_GUIDELINES.md and the Quick Start wiki link.

Daily commands:

# Development build
make clean && make all
# Run as nested Wayland session (in X11 or another Wayland compositor)
HYPRLAND_LOG_WLR=1 ./build/bin/hyprland
# Or install and run as display server
# See example/hyprland.service for systemd integration

Key cautions & unknowns

  • Concentrated ownership — top contributor handles 50% of recent commits
  • Build environment: Requires full Wayland development stack (libwayland, wayland-protocols, libxkbcommon, etc.); CMake is strict about compiler flags (see .clang-tidy). Nix ecosystem heavy:…
  • Published-advisory coverage was unavailable for the captured dependencies.
  • Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

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.

Save as

Full context for agent files, or a concise PDF for human review.

View complete agent reference

Open to load every section of the agent reference.

Want this for your own repo?

Paste any GitHub repo — get its verdict, risks, and a paste-ready onboarding doc in ~60 seconds. Free, no sign-up.

Embed the "Healthy" badge

Paste into your README — live-updates from the latest cached analysis.

Variant:
RepoPilot: Healthy
[![RepoPilot: Healthy](https://repopilot.app/api/badge/hyprwm/hyprland)](https://repopilot.app/r/hyprwm/hyprland)

Paste at the top of your README.md — renders inline like a shields.io badge.

Preview social card

This card auto-renders when someone shares https://repopilot.app/r/hyprwm/hyprland on X, Slack, or LinkedIn.

Ask AI about hyprwm/hyprland

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question
Embed this chat in your README

Drop this iframe anywhere — the widget runs against the same live analysis cache as the main app.

<iframe
  src="https://repopilot.app/embed/hyprwm/hyprland"
  width="100%" height="500"
  style="border:1px solid #d0d7de; border-radius:8px;"
  allow="microphone"
  loading="lazy"
></iframe>