hacs/default — The home of the default HACS repositories.

Description and use

**Brief summary**
The hacs/default repository is the curated collection of default Home Assistant Community Store (HACS) add‑ons, serving as the reference point for the standard set of integrations that HACS can install out of the box. With a solid base of community interest (over 570 ★ and 2.7 k forks) and recent activity, it provides a convenient starting point for Home Assistant users who want a ready‑made catalogue of vetted plugins.

**Value**

• **Centralized source** – All default HACS add‑ons are listed in one place, eliminating the need to hunt across multiple repos.
• **Community‑backed** – The star and fork counts show broad adoption, indicating that many users already rely on this set for their Home Assistant setups.
• **Up‑to‑date** – The repo is actively maintained (last commit 2026‑05‑11), helping to keep the default add‑ons compatible with the latest Home Assistant releases.

**Practical adoption path**

1. **Review the README** to understand the selection criteria and verify that the listed add‑ons align with your project’s requirements.
2. **Clone or add the repo as a HACS source** in your Home Assistant instance, then run HACS’s “Refresh” to import the default catalog.
3. **Perform a manual audit** of each add‑on you plan to use—check licensing, security advisories, and the maintainers’ activity, as the repository’s metadata is sparse.
4. **Pin versions** of the chosen add‑ons in your configuration to guard against unexpected breaking changes.

**Production readiness**
The project sits at a medium readiness level: it is suitable for prototypes, internal environments, or as a baseline for production deployments, provided you conduct the recommended due‑diligence checks (license compliance, security review, and maintainer responsiveness). Once those checks are completed and you have locked down the specific add‑ons you need, hacs/default can be safely promoted to production use.

Problem

hacs/default may be useful when its README and activity match a concrete workflow.

Outcome

Medium: useful for prototypes or internal workflows, with dependency and maintenance checks before production.

Evidence

The home of the default HACS repositories.

Source