Versioned security assessment

Report ID: SA-D5062C00

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

sleek-design-mobile-apps security assessment v3

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
sleek-design-mobile-apps
Version
v3
Maintainer
sleekdotdesign
Coverage
1 Files scanned · 435 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

2 confirmed security findings require attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or 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.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

1 Files scanned · 435 Lines analyzed

19 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 6 evidence locations

Filesystem access

May read or write local files.

Not recorded by this audit

Env variables

May read values from the process environment.

Observed in 11 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 118 evidence locations

Capability review items (17)
High
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.
High
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.
High
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.
High
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.
High
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.
High
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.
High
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.
High
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.
High
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.
High
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.
High
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.
Low
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.
Low
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.
Low
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.
Low
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.
Low
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.
Low
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.

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (2)

RISK-001 Medium
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 Medium
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.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    High
    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
    Medium
    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
    Medium
    Destructive project deletion
    Require explicit confirmation with the project name and project id before calling DELETE /api/v1/projects/:id.
  4. FIX-004
    Low
    Scanner noise from Markdown backticks
    Keep API examples clearly fenced and state that the skill does not include executable scripts or shell commands.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Verify and export

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable