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-D5062C00

7/7/2026, 5:43:09 AM

sleek-design-mobile-apps evaluación de seguridad v3

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
sleek-design-mobile-apps
Versión
v3
Mantenedor
sleekdotdesign
Fuente
github.com/sleekdotdesign/agent-skills/tree/main/skills/design-mobile-apps/
Cobertura
1 Archivos escaneados · 435 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.

Most external command findings are false positives caused by Markdown backticks and API examples, not executable code. Real risks remain because the skill requires SLEEK_API_KEY, makes bearer-authenticated requests to https://sleek.design, sends user prompts or image URLs to Sleek, and documents project deletion. No evidence of prompt injection, hidden command execution, or unauthorized third-party hosts was found.

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

1 Archivos escaneados · 435 Líneas analizadas

19 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 6 ubicaciones de evidencia

Acceso al sistema de archivos

Puede leer o escribir archivos locales.

No registrado por esta auditoría

Variables de entorno

Puede leer valores del entorno del proceso.

Observado en 11 ubicaciones de evidencia

Comandos externos

Puede invocar comandos o programas fuera de la habilidad.

Observado en 118 ubicaciones de evidencia

Elementos de revisión de capacidades (17)
Alto
SKILL.md:4
Generic API/secret keys
compatibility: Requires SLEEK_API_KEY environment variable. Network access limited to https://sleek.
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Alto
SKILL.md:6
Generic API/secret keys
requires-env: SLEEK_API_KEY
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Alto
SKILL.md:17
Generic API/secret keys
**Auth**: `Authorization: Bearer $SLEEK_API_KEY` on every `/api/v1/*` request
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Alto
SKILL.md:25
Generic API/secret keys
Create API keys at **https://sleek.design/dashboard/api-keys**. The full key value is shown only onc
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Alto
SKILL.md:104
Generic API/secret keys
Authorization: Bearer $SLEEK_API_KEY
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Alto
SKILL.md:128
Generic API/secret keys
Authorization: Bearer $SLEEK_API_KEY
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Alto
SKILL.md:151
Generic API/secret keys
Authorization: Bearer $SLEEK_API_KEY
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Alto
SKILL.md:180
Generic API/secret keys
Authorization: Bearer $SLEEK_API_KEY
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Alto
SKILL.md:243
Generic API/secret keys
Authorization: Bearer $SLEEK_API_KEY
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Alto
SKILL.md:297
Generic API/secret keys
Authorization: Bearer $SLEEK_API_KEY
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Alto
SKILL.md:429
Generic API/secret keys
| Sending to `/api/v1` without `Authorization` header | Add `Authorization: Bearer $SLEEK_API_KEY` t
The skill requires SLEEK_API_KEY and instructs agents to use it as a bearer token for Sleek API calls. This is expected, but misuse of the token could access, modify, screenshot, or delete Sleek projects.
Bajo
SKILL.md:4
Hardcoded URL
compatibility: Requires SLEEK_API_KEY environment variable. Network access limited to https://sleek.
The skill explicitly requires outbound HTTPS requests to https://sleek.design. This is intended and single-host, but user content leaves the local environment.
Bajo
SKILL.md:7
Hardcoded URL
allowed-hosts: https://sleek.design
The skill explicitly requires outbound HTTPS requests to https://sleek.design. This is intended and single-host, but user content leaves the local environment.
Bajo
SKILL.md:16
Hardcoded URL
**Base URL**: `https://sleek.design`
The skill explicitly requires outbound HTTPS requests to https://sleek.design. This is intended and single-host, but user content leaves the local environment.
Bajo
SKILL.md:25
Hardcoded URL
Create API keys at **https://sleek.design/dashboard/api-keys**. The full key value is shown only onc
The line directs users to the external Sleek dashboard for API key setup. This is legitimate onboarding, but it confirms the skill depends on an external service.
Bajo
SKILL.md:46
Hardcoded URL
- **Single host**: All requests go exclusively to `https://sleek.design`. No data is sent to third p
The skill explicitly requires outbound HTTPS requests to https://sleek.design. This is intended and single-host, but user content leaves the local environment.
Bajo
SKILL.md:186
Hardcoded URL
"imageUrls": ["https://example.com/ref.png"],
The example shows imageUrls being sent as visual context, and the skill states Sleek servers may fetch those URLs. This is documented behavior but carries data-sharing risk.

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
SKILL.md:49SKILL.md:58SKILL.md:176SKILL.md:186
User Content Sent to External AI Service
The skill instructs agents to send the user design request directly as message.text and allows image URLs that Sleek servers may fetch. Sensitive prompts or private images could leave the user environment.
The documentation explicitly says to use the user words directly in message.text and warns that image URLs are fetched by Sleek servers. This strongly supports a third-party data-transfer risk, although it is documented and intentional.
RISK-002 Medio
SKILL.md:34SKILL.md:86SKILL.md:138-141
Destructive Project Deletion Capability
The skill documents DELETE /api/v1/projects/:id and the projects:write scope. A broad Sleek API key could allow project deletion if the user request is misunderstood or lacks confirmation.
The endpoint table and example section explicitly include project deletion, and the documented projects:write scope enables create and delete operations. The risk depends on token scope and user confirmation practices.

Medidas correctivas

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

  1. FIX-001
    Alto
    API key exposure and broad scopes
    Use the narrowest Sleek API key scopes needed for each task and never log Authorization headers or full key values.
  2. FIX-002
    Medio
    External transfer of prompts and image URLs
    Ask before sending sensitive prompts or private image URLs to Sleek, and redact confidential information before submission.
  3. FIX-003
    Medio
    Destructive project deletion
    Require explicit confirmation with the project name and project id before calling DELETE /api/v1/projects/:id.
  4. FIX-004
    Bajo
    Scanner noise from Markdown backticks
    Keep API examples clearly fenced and state that the skill does not include executable scripts or shell commands.

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

Informe JSON CITATION.cff SARIF 2.1.0 Manifiesto de instalación firmado

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