updated 2026-08-12 05:02 UTC

Home Assistant Vibecode Agent

Coolver/home-assistant-vibecode-agent

Home Assistant MCP server agent. Enable Claude Code, Cursor, VS Code or any MCP-enabled IDE to help you vibe-code and ma

MCP Servers Python Grade D Listed MIT
21.1/100
Rank #1015 of 1283
Compare Home Assistant Vibecode Agent

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-03 · 9d ago
Recent change
New

Is Home Assistant Vibecode Agent safe? Home Assistant Vibecode Agent scores 21.1/100 (Grade D), ranked #1015 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 16% of recent commits are signed; last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#537 IT Glue — 21.1 (D) → #538 Devcontainer MCP — 21.1 (D) → #540 Storeshots MCP — 21.1 (D) → #541 Serpapi MCP — 21.0 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #1005
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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
56.0
Activity sub-score · out of 100
#539
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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 9 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
610
Forks
50
Last Push
2026-08-03
9 days ago
Commits (4 wk)
3?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▼7
was #1008

Analysis

HVTrust Dimensions vs MCP Servers

21.1 / 100 · 50.0% confidence

Home Assistant Vibecode Agent MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.8 / 25
4.2 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
12.6 / 20
in line with avg 12.4
AdoptionLog-scaled stars · package downloads
6.7 / 20
0.9 above avg 5.8

Activity Inputs

56.0 / 100
StarsRepository reach
16.7 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
7.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
16%
of last 100 commits verified

Is Home Assistant Vibecode Agent safe?

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?
No OpenSSF Scorecard data is currently published for Home Assistant Vibecode Agent. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Home Assistant Vibecode Agent actively maintained?
Maintained. Last push was 9 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?
16% 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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface 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

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
Listed 1
2026-08-10
Newly Listed
First tracked at rank #1005
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 21.1 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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON