updated 2026-10-11 08:08 UTC

Home Assistant Vibecode Agent

Repository Website by Coolver

Home Assistant MCP server agent. Enable Claude Code, Cursor, VS Code or any MCP-enabled IDE to help you vibe-code and manage Home Assistant: create and debug automations, design dashboards, tweak themes, modify configs, and deploy changes using natural language

MCP Servers Python Listed MIT

Is Home Assistant Vibecode Agent safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.0 / 10
Provenance None
Signed commits 17%
Last push 24d ago
Compare Home Assistant Vibecode Agent

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Home Assistant Vibecode Agent scores 48.3/100 (Grade D), ranked #1027 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.0/10; 17% of recent commits are signed; last pushed 2026-09-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How Home Assistant Vibecode Agent could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Home Assistant Vibecode Agent and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/Coolver/home-assistant-vibecode-agent, MIT, last pushed 2026-09-17. 17% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.0/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 2
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 4
    Packaging -1
    Pinned-Dependencies 1
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 9
    Vulnerabilities 0

  3. Published packages None

    No registry package. Home Assistant Vibecode Agent is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 3.8/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Home Assistant Vibecode Agent’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Home Assistant Vibecode Agent compares in MCP Servers

  1. #588 MCP Slim Guard 48.3 ±0
  2. #589 Linkup MCP Server 48.3 ±0
  3. #590 Home Assistant Vibecode Agent 48.3 this agent
  4. #591 Obsidian Vault MCP 48.2 −0.1
  5. #592 Appstore Connect MCP 48.2 −0.1

Bars show each HVTrust score; the tick marks Home Assistant Vibecode Agent’s 48.3.

Where the 48.3 comes from

HVTrust dimensions vs the MCP Servers average

48.3 / 100 · 100.0% confidence

Home Assistant Vibecode Agent MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.9 / 25
4.5 below avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
11.9 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
12.3 / 20
in line with avg 12.2
AdoptionLog-scaled stars · package downloads
6.7 / 20
0.7 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 17 spots (#999 → #1016)
2026-09-30
Rank Moved
Rank dropped 11 spots (#962 → #973)
2026-09-26
Rank Moved
Rank rose 24 spots (#981 → #957)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Home Assistant Vibecode Agent View MCP Servers Report missing data
52.6
Activity sub-score · out of 100
#590
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 08:08 UTC · Repo last pushed 24 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
635
Forks
52
Last Push
2026-09-17
24 days ago
Commits (4 wk)
2
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
11
Rank Change
▼4
was #1023

Analysis

Activity Inputs

52.6 / 100
StarsRepository reach
16.8 / 30
FreshnessLast push recency
21.7 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
8.0 / 20

Common questions about Home Assistant Vibecode Agent

Public trust evidence for Home Assistant Vibecode Agent is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Home Assistant Vibecode Agent publish package provenance?
No published build provenance is currently detected for Home Assistant Vibecode Agent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Home Assistant Vibecode Agent have an OpenSSF Scorecard?
Home Assistant Vibecode Agent has an OpenSSF Scorecard score of 4.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Home Assistant Vibecode Agent actively maintained?
Maintained. Last push was 24 days ago.
What license does Home Assistant Vibecode Agent use?
Home Assistant Vibecode Agent ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Home Assistant Vibecode Agent's commits signed?
17% of the last 100 commits to Home Assistant Vibecode Agent are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
Home Assistant Vibecode Agent appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • code
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Home Assistant Vibecode Agent's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain Home Assistant Vibecode Agent?

For maintainers

HVTrust scores Home Assistant Vibecode Agent from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 25HVTrust 3Listed 2Score 2Scorecard 1Surface 1Delisted 1MCP 1
2026-10-09
Rank Moved
Rank dropped 17 spots (#999 → #1016)
2026-09-30
Rank Moved
Rank dropped 11 spots (#962 → #973)
2026-09-26
Rank Moved
Rank rose 24 spots (#981 → #957)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 463 spots (#526 → #989)
2026-09-23
HVTrust Changed
HVTrust up 9.0pts (39.1 → 48.1)
2026-09-22
Newly Listed
First tracked at rank #526
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 32 spots (#943 → #975)
2026-09-17
Rank Moved
Rank rose 120 spots (#1063 → #943)
2026-09-17
HVTrust Changed
HVTrust up 4.8pts (44.5 → 49.3)
2026-09-17
Activity Score Changed
Activity score up 12pts (44 → 56)
2026-09-12
Rank Moved
Rank dropped 13 spots (#1051 → #1064)
2026-09-09
Rank Moved
Rank dropped 18 spots (#1026 → #1044)
2026-09-08
Rank Moved
Rank dropped 12 spots (#1014 → #1026)
2026-09-07
Rank Moved
Rank dropped 35 spots (#979 → #1014)
2026-09-06
Rank Moved
Rank dropped 15 spots (#964 → #979)
2026-09-05
Rank Moved
Rank dropped 49 spots (#915 → #964)
2026-09-04
Rank Moved
Rank dropped 26 spots (#889 → #915)
2026-09-03
Rank Moved
Rank dropped 54 spots (#835 → #889)
2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-09-02
Rank Moved
Rank dropped 90 spots (#745 → #835)
2026-09-02
Activity Score Changed
Activity score down 6pts (52 → 46)
2026-09-01
Rank Moved
Rank dropped 30 spots (#715 → #745)
2026-08-31
Rank Moved
Rank dropped 47 spots (#668 → #715)
2026-08-30
Scorecard Added
OSSF Scorecard: 3.8/10
2026-08-30
Rank Moved
Rank rose 503 spots (#1171 → #668)
2026-08-30
HVTrust Changed
HVTrust up 26.9pts (20.6 → 47.5)
2026-08-29
Rank Moved
Rank dropped 23 spots (#1148 → #1171)
2026-08-28
Rank Moved
Rank dropped 22 spots (#1126 → #1148)
2026-08-27
Rank Moved
Rank dropped 17 spots (#1109 → #1126)
2026-08-26
Rank Moved
Rank dropped 67 spots (#1042 → #1109)
2026-08-24
Rank Moved
Rank dropped 11 spots (#1028 → #1039)
2026-08-17
Rank Moved
Rank rose 13 spots (#1040 → #1027)
2026-08-16
Rank Moved
Rank dropped 29 spots (#1011 → #1040)
2026-08-10
Newly Listed
First tracked at rank #1005
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 48.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/home-assistant-vibecode-agent.svg)](https://hvtracker.net/agents/home-assistant-vibecode-agent)
HTML:
<a href="https://hvtracker.net/agents/home-assistant-vibecode-agent"><img src="https://hvtracker.net/badge/home-assistant-vibecode-agent.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON