Versioned security assessment

Report ID: SA-E06E43F4

6/30/2026, 1:00:34 AM

expo-api-routes security assessment v3

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
expo-api-routes
Version
v3
Maintainer
expo
Source
github.com/expo/skills/tree/main/plugins/expo-app-design/skills/expo-api-routes/
Coverage
1 Files scanned · 369 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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.

Static analysis flagged many shell, network, filesystem, environment, and weak crypto patterns, but most are false positives from Markdown code fences, inline code, route examples, or legitimate server-side configuration guidance. Human review found no prompt injection or malicious behavior, but several copyable examples could lead to insecure implementations if used without additional hardening.

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 · 369 Lines analyzed

6 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 10 evidence locations

Filesystem access

May read or write local files.

Observed in 1 evidence location

Env variables

May read values from the process environment.

Observed in 6 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 48 evidence locations

Capability review items (6)
Medium
SKILL.md:165-178
Overly Permissive CORS Example Allows Authorization Headers
The CORS example allows any origin while also allowing the Authorization header. If copied into a production API, this can expose authenticated endpoints to browser calls from untrusted origins unless additional authentication and origin checks are added.
The code is a documentation example, not executable skill code, but the insecure CORS pattern is explicit and copyable. The risk depends on how users adapt the example in production.
Medium
SKILL.md:349-354
External API Proxy Example Does Not Encode User Input
The weather proxy example interpolates a query parameter directly into an external API URL with an API key. A copied implementation could allow query manipulation and unreliable upstream requests unless the value is validated and encoded.
The host is hardcoded, so this is not clear SSRF, but direct interpolation of request-controlled input into a URL is visible. The issue is a realistic implementation risk for copied example code.
Low
SKILL.md:200-210SKILL.md:217-225
Shell Command Examples Are Documentation, Not Hidden Execution
The analyzer flagged many Markdown backticks and bash examples as command execution. These commands are visible installation, login, local testing, curl, and deployment examples rather than code that the skill runs automatically.
The relevant text is inside Markdown fences and no helper script or hidden executable file is present. The commands are ordinary Expo and HTTP testing workflows.
Low
SKILL.md:132-143SKILL.md:289-291SKILL.md:352-353
Environment Variable Examples Are Legitimate Server-Side Guidance
The skill demonstrates server-side use of environment variables for API keys and database credentials. This is appropriate for API routes, though the examples should remind users to avoid command history exposure and to use secret managers where available.
The skill explicitly says secrets belong server-side and warns never to commit local env files. No evidence shows exfiltration or collection of environment values by the skill itself.
Low
SKILL.md:232-234
Secret Value Placeholder Appears In Command Example
The EAS environment command uses a placeholder API key value in a shell command. The placeholder is not a real secret, but real values passed this way can appear in shell history or process listings.
The value shown is clearly a placeholder, which lowers severity. The command pattern can still teach a less safe secret entry method if copied with a real value.
Low
SKILL.md:335-336
Relative Import Misclassified As Path Traversal
The path traversal finding points to a TypeScript relative import from a route file to a utility module. It is not file access and does not read user-controlled paths.
The flagged sequence appears only in an import path inside a code example. There is no filesystem API call or user input involved.

Risk findings

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

No confirmed security findings were recorded for this completed audit.

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.

Static false positives ignored (1)
Low
SKILL.md:3SKILL.md:258-262SKILL.md:364
Weak Cryptography Detection Is A False Positive
The weak cryptography detections do not correspond to use of MD5, SHA-1, DES, or another weak primitive. The only crypto example uses SHA-256 through Web Crypto.
Line 258 through 262 shows SHA-256, which is not the weak algorithm category flagged by the analyzer. The other flagged lines are prose and status-code guidance, not cryptographic code.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

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

Audit attestation: not_attestable