Repo brief: glzr-io/zebar

Generated by RepoPilot · document generated 2026-09-13 · concise human review Evidence snapshot · analyzed 2026-09-13T19:47:43.245Z · commit 6aa335f741a2

Verdict

Mixed — Mixed signals — read the receipts

• Last commit 5w ago
• 19 active contributors
• GPL-3.0 licensed
• CI configured

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

What it is

Zebar is a cross-platform desktop widget framework that uses native webviews to render customizable taskbars, desktop widgets, and popups written in HTML/CSS/TypeScript. It runs on Windows, macOS, and Linux, with a widget marketplace for distribution and a local development workflow using zpack.json manifests stored in ~/.glzr/zebar/. Monorepo structure: packages/desktop contains the main Rust application (webview host + system tray + marketplace client), crates/ holds reusable Rust libraries (komorebi-util for window management, shell-util for shell integration, systray-util for tray icon handling). TypeScript lives in packages/client-api and user widget packs. Desktop app is the…

Start here

Open these first:

• packages/client-api/src/index.ts — Main entry point for the client API; exposes all public interfaces for widget configuration, providers, and desktop controls.
• packages/client-api/src/providers/create-provider.ts — Core provider factory pattern; understanding this is essential for adding new data providers (audio, battery, CPU, etc.).
• packages/client-api/src/config/widget-config.ts — Widget configuration schema and validation; defines how users declare and customize widgets.
• packages/client-api/src/desktop/widgets.ts — Widget lifecycle management and rendering; handles creation, updates, and destruction of widget instances.
• packages/client-api/src/config/widget-pack.ts — Widget pack loading and distribution; manages how widget bundles are discovered and loaded into Zebar.

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/glzr-io/zebar.git
cd zebar
npm install
cargo build --release

Refer to CONTRIBUTING.md for platform-specific build steps and Node.js version (see .nvmrc). For widget development, use the Zebar GUI to create packs in ~/.glzr/zebar/ or scaffold via 'Create new pack'.

Daily commands:

Dev build: cargo build (debug) or cargo build --release (optimized). Start Zebar desktop app via packages/desktop. Widget development: scaffold a pack in ~/.glzr/zebar/<pack-name>/, edit zpack.json, run template-spe…

…shortened for this brief.

Key cautions & unknowns

• Concentrated ownership — top contributor handles 73% of recent commits
• GPL-3.0 is copyleft — check downstream compatibility
• No Electron: native webview host is custom; debug tooling differs from Electron (check .vscode/launch.json). Windows API complexity: extensive windows 0.58 feature flags are tightly coupled; changing them…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

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.