Подтверждённые проблемы безопасности (2) требуют внимания.
Контекст установки
Исторические доказательства
Этот отчёт может не описывать артефакт, доступный для установки в настоящее время. Откройте текущую страницу Навыка для получения рекомендаций по установке.
Этот отчёт не блокирует и не разрешает манифест или 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.
Позиция отчета
Исторический отчет
Откройте историю аудита перед использованием этого отчета для установки.
Аттестация аудита
Не подлежит аттестации
Требуемая неизменяемая привязка не завершена.
Проверка человеком
Не проверено
Для этого отчета не зафиксирована проверка человеком.
Этот отчёт не заявляет о выполнении во время работы или в песочнице и не доказывает отсутствие побочных эффектов.
01
Цепочка доказательств
Проследите доказательства от привязки источника до контракта установки. Доступные доказательства подтверждают возможность проверки; они не являются гарантией безопасности.
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.
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.
**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.
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.
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.
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.
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.
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.
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.
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.
| 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.
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.
The skill explicitly requires outbound HTTPS requests to https://sleek.design. This is intended and single-host, but user content leaves the local environment.
The skill explicitly requires outbound HTTPS requests to https://sleek.design. This is intended and single-host, but user content leaves the local environment.
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.
- **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.
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.
03
Результаты оценки рисков
Подтверждённые проблемы безопасности отделены от элементов, которые всё ещё требуют проверки.
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.
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.
04
Меры по устранению
В ходе этого аудита были зафиксированы рекомендуемые исправления. Их применение является ответственностью сопровождающего.
FIX-001
Высокий
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.
FIX-002
Средний
External transfer of prompts and image URLs
Ask before sending sensitive prompts or private image URLs to Sleek, and redact confidential information before submission.
FIX-003
Средний
Destructive project deletion
Require explicit confirmation with the project name and project id before calling DELETE /api/v1/projects/:id.
FIX-004
Низкий
Scanner noise from Markdown backticks
Keep API examples clearly fenced and state that the skill does not include executable scripts or shell commands.
05
Экспертные доказательства
Неизменяемая идентификация субъекта, метаданные сканера, отклонённые совпадения и доказательства на уровне источника.
Субъект артефакта
Коммит Marketplace
Недоступно
Хеш содержимого
Недоступно
Хеш дерева
Недоступно
Путь Skill
Недоступно
Хеш данных аудита
Недоступно
Метаданные анализа
Модель аудита: codex
Состояние анализа: Завершено
Область действия ограничена зафиксированными файлами, строками, методами и доказательствами. Выполнение во время работы или в песочнице не заявляется.