Este informe no está traducido al idioma solicitado. Se muestra en su lugar el informe canónico en inglés.

Evaluación de seguridad versionada

ID del informe: SA-B959EBFD

7/9/2026, 4:31:55 PM

home-assistant-manager evaluación de seguridad v8

Informe de certificación de seguridad de la habilidad

Historial de auditorías
Modelo de auditoría: codex Informe histórico
Nombre de la habilidad
home-assistant-manager
Versión
v8
Mantenedor
komal-SkyNET
Cobertura
3 Archivos escaneados · 1,023 Líneas analizadas
Versión de la política
No disponible

Gravedad máxima de hallazgo confirmada

Medio

2 hallazgos de seguridad confirmados requieren atención.

Contexto de instalación

Evidencia histórica

Este informe podría no describir el artefacto instalable actualmente. Abra la página actual de la Skill para obtener orientación de instalación.

Abrir la página actual de la habilidad

Este informe no bloquea ni autoriza el manifiesto ni el ZIP.

The skill is not malicious, but it intentionally guides privileged Home Assistant operations through SSH, hass-cli, git, and scp. Confirmed risks center on remote command execution, writing Home Assistant .storage files, persistent token setup, and commands that can affect real devices; many scanner hits were Markdown, template, or screenshot false positives. No prompt injection attempt was found in the reviewed files.

Posición del informe

Informe histórico

Abra el historial de auditorías antes de usar este informe para instalar.

Atestación de auditoría

No se puede certificar

La vinculación inmutable requerida está incompleta.

Verificación humana

No verificado

No se ha registrado ninguna verificación humana para este informe.

Cobertura

3 Archivos escaneados · 1,023 Líneas analizadas

35 elementos mostrados para revisión

Limitaciones

Este informe no afirma ninguna ejecución en tiempo de ejecución ni en entorno aislado y no prueba la ausencia de efectos secundarios.

Cadena de evidencias

Sigue la evidencia desde la vinculación del código fuente hasta el contrato de instalación. La evidencia disponible permite la verificación; no constituye una garantía de seguridad.

  1. Fuente

    Vinculación no disponible

  2. Artefacto

    Identidad incompleta

  3. Auditoría

    Completo

  4. Contrato de instalación

    Abrir el manifiesto para verificar

    Abrir el manifiesto

Capacidades observadas

Observado significa que este informe registró evidencia de respaldo. No registrado no prueba que una capacidad esté ausente.

Contiene scripts

Puede ejecutar código incluido con la habilidad.

No registrado por esta auditoría

Acceso a red

Puede conectarse a servicios externos.

Observado en 3 ubicaciones de evidencia

Acceso al sistema de archivos

Puede leer o escribir archivos locales.

Observado en 7 ubicaciones de evidencia

Variables de entorno

Puede leer valores del entorno del proceso.

Observado en 1 ubicación de evidencia

Comandos externos

Puede invocar comandos o programas fuera de la habilidad.

Observado en 88 ubicaciones de evidencia

Elementos de revisión de capacidades (33)
Alto
Hidden file in home directory
# Set environment variables (add to ~/.bashrc or ~/.zshrc)
The README advises adding Home Assistant environment variables to ~/.bashrc or ~/.zshrc, and the nearby setup includes a long-lived access token. Persisting control tokens in shell startup files increases exposure.
Medio
Hidden file access
# Set environment variables (add to ~/.bashrc or ~/.zshrc)
The README directs users to modify hidden shell startup files for Home Assistant environment variables. This is common setup guidance, but it can persist sensitive access tokens broadly.
Medio
Ruby/shell backtick execution
1. SSH access to Home Assistant instance (`root@homeassistant.local`)
The skill requires SSH access to root@homeassistant.local, enabling privileged remote management of Home Assistant. This is intended functionality, but it can change or restart the user system.
Medio
Ruby/shell backtick execution
2. `hass-cli` installed locally
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medio
Ruby/shell backtick execution
All `hass-cli` commands use environment variables automatically:
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medio
Ruby/shell backtick execution
```bash
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medio
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medio
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medio
Ruby/shell backtick execution
Use `scp` for quick testing before committing:
The workflow instructs copying files to the Home Assistant instance with scp. This can overwrite configuration or dashboard files, so it is a real operational risk even though it is not malicious.
Medio
Ruby/shell backtick execution
```bash
The workflow instructs copying files to the Home Assistant instance with scp. This can overwrite configuration or dashboard files, so it is a real operational risk even though it is not malicious.
Medio
Ruby/shell backtick execution
- ✅ Automations: `hass-cli service call automation.reload`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medio
Ruby/shell backtick execution
- ✅ Scripts: `hass-cli service call script.reload`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medio
Ruby/shell backtick execution
- ✅ Scenes: `hass-cli service call scene.reload`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medio
Ruby/shell backtick execution
- ✅ Template entities: `hass-cli service call template.reload`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medio
Ruby/shell backtick execution
- ✅ Groups: `hass-cli service call group.reload`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medio
Ruby/shell backtick execution
- ✅ Themes: `hass-cli service call frontend.reload_themes`
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medio
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medio
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medio
Ruby/shell backtick execution
```bash
The skill instructs use of hass-cli with Home Assistant credentials to query state or call services. This is intended management behavior, but service calls can alter the running home automation system.
Medio
Ruby/shell backtick execution
```bash
The workflow manually triggers an automation through hass-cli. Triggering automations can send notifications or actuate connected devices, so user confirmation is needed.
Medio
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medio
Ruby/shell backtick execution
```bash
The command reads Home Assistant entity state through authenticated hass-cli access. It is mostly read-only, but it exposes household state data and depends on sensitive credentials.
Medio
Ruby/shell backtick execution
```bash
The command reads Home Assistant entity state through authenticated hass-cli access. It is mostly read-only, but it exposes household state data and depends on sensitive credentials.
Medio
Ruby/shell backtick execution
```bash
The workflow instructs copying files to the Home Assistant instance with scp. This can overwrite configuration or dashboard files, so it is a real operational risk even though it is not malicious.
Medio
Ruby/shell backtick execution
```bash
The workflow instructs copying files to the Home Assistant instance with scp. This can overwrite configuration or dashboard files, so it is a real operational risk even though it is not malicious.
Medio
Ruby/shell backtick execution
```bash
The command reads Home Assistant entity state through authenticated hass-cli access. It is mostly read-only, but it exposes household state data and depends on sensitive credentials.
Medio
Ruby/shell backtick execution
```bash
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medio
Ruby/shell backtick execution
1. **Always check configuration** before restart: `ha core check`
The documented workflow runs SSH, git, or Home Assistant CLI operations against the remote /config environment. These commands are legitimate for this skill but carry operational risk if run without confirmation.
Medio
Hidden file access
scp .storage/lovelace.control_center root@homeassistant.local:/config/.storage/
This command copies files into Home Assistant .storage over SSH. That can alter dashboard configuration or registry data, so it is sensitive even when used for legitimate dashboard management.
Medio
Hidden file access
scp .storage/lovelace.new_dashboard root@homeassistant.local:/config/.storage/
This command copies files into Home Assistant .storage over SSH. That can alter dashboard configuration or registry data, so it is sensitive even when used for legitimate dashboard management.
Medio
Hidden file access
scp .storage/lovelace_dashboards root@homeassistant.local:/config/.storage/
This command copies files into Home Assistant .storage over SSH. That can alter dashboard configuration or registry data, so it is sensitive even when used for legitimate dashboard management.
Medio
Hidden file access
scp .storage/lovelace.my_dashboard root@homeassistant.local:/config/.storage/
This command copies files into Home Assistant .storage over SSH. That can alter dashboard configuration or registry data, so it is sensitive even when used for legitimate dashboard management.
Bajo
Hardcoded URL
claude mcp add --transport http context7 https://mcp.context7.com/mcp \
The README configures Claude MCP to use the external Context7 endpoint. This is optional documentation access, but it sends requests and a user API key header to a third-party service.

Hallazgos de riesgos

Las preocupaciones de seguridad confirmadas están separadas de los elementos que aún deben revisarse.

Preocupaciones de seguridad confirmadas (2)

RISK-001 Medio
Long-Lived Home Assistant Token in Shell Profile
The README tells users to add HASS_SERVER and HASS_TOKEN values to shell startup files. A Home Assistant token stored there can be exposed to shells, subprocesses, backups, or accidental sharing.
The setup instructions explicitly name ~/.bashrc or ~/.zshrc and then export HASS_TOKEN on the following line. This is a real secret persistence risk, although it is normal setup guidance rather than malicious behavior.
RISK-002 Medio
Automation Trigger Commands Can Affect Physical Devices
The skill encourages manual Home Assistant automation triggers and service calls during verification. Depending on the target automation, these actions can affect locks, climate, lights, notifications, or other connected devices.
The cited workflow directly invokes automation.trigger and common service-call commands. The impact depends on the user environment, but the physical-device side effect risk is clear.

Medidas correctivas

Esta auditoría registra correcciones sugeridas. Aplicarlas es responsabilidad de la persona encargada del mantenimiento.

  1. FIX-001
    Alto
    Long-lived tokens in shell startup files
    Recommend a secret manager, session-scoped environment variables, or restricted credentials where possible. Warn users not to commit, log, screenshot, or share HASS_TOKEN values.
  2. FIX-002
    Medio
    Privileged remote Home Assistant commands
    Require explicit user confirmation before SSH, scp, hass-cli service calls, automation triggers, git pull on /config, reloads, or restarts. Show the exact target host and expected side effects first.
  3. FIX-003
    Medio
    Direct writes to Home Assistant .storage files
    Back up .storage files before copying, validate dashboard JSON first, and require review before modifying lovelace_dashboards or restarting Home Assistant.
  4. FIX-004
    Bajo
    Optional third-party Context7 MCP endpoint
    Document that Context7 uses an external network service and a user-provided API key. Keep that key out of shared configuration and logs.

Evidencia experta

Identidad inmutable del sujeto, metadatos del escáner, coincidencias descartadas y evidencia a nivel de código fuente.

Sujeto del artefacto

Commit de Marketplace
No disponible
Hash del contenido
No disponible
Hash del árbol
No disponible
Ruta del Skill
No disponible
Hash de la carga de auditoría
No disponible

Metadatos del análisis

Modelo de auditoría: codex

Estado del análisis: Completo

El alcance se limita a los archivos, líneas, métodos y pruebas registrados. No se afirma ninguna ejecución en tiempo de ejecución ni en entorno aislado.

Verificar y exportar

El manifiesto y el archivo de bloqueo vinculan los artefactos de instalación a hashes criptográficos. Esta afirmación de integridad es independiente de la evaluación de seguridad.

Atestación de auditoría: not_attestable