Skills uvicorn Audit History
📦

Audit History

uvicorn - 8 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v8 LatestJul 23, 2026, 11:12 AM No confirmed findings5No capability change
v7 Jul 7, 2026, 10:19 PM 1 confirmed0No capability change
v6 Jul 6, 2026, 06:16 AM 1 confirmed0No capability change
v5 Jun 28, 2026, 04:20 PM No confirmed findings2No capability change
v4 Jan 16, 2026, 08:08 PM No confirmed findings0No capability change
v3 Jan 16, 2026, 08:08 PM No confirmed findings0No capability change
v2 Jan 11, 2026, 04:16 AM No confirmed findings0No capability change
v1 Jan 11, 2026, 04:16 AM No confirmed findings0Baseline

Jul 23, 2026, 11:12 AM

The 45 external-command alerts are false positives caused by Markdown fences and inline option formatting; no backtick execution exists. Temporary socket usage, placeholder TLS paths, container binding, loopback documentation, and worker-option text are legitimate examples. Five examples bind to all interfaces without sufficient exposure warnings, and four also use development reload settings.

1
Files scanned
232
Lines analyzed
8
Review items
0
False positives ignored
Capability review items (5)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium
Hardcoded IP address
uv run uvicorn main:app --host 0.0.0.0 --port 8000
The example binds Uvicorn to every network interface without an exposure warning. This can make an unprotected application reachable from other hosts.
Medium
Hardcoded IP address
uvicorn.run("main:app", host="0.0.0.0", port=8000, reload=True)
The programmatic example combines an all-interface bind with reload mode. This can expose a development server and its changing code to the network.
Medium
Hardcoded IP address
export UVICORN_HOST="0.0.0.0"
The environment configuration binds all interfaces and enables reload before starting Uvicorn. No warning or access-control requirement accompanies the example.
Medium
Hardcoded IP address
--host 0.0.0.0 \
The combined CLI example binds all interfaces and enables reload. It can expose a development server beyond the local machine.
Medium
Hardcoded IP address
command: uvicorn main:app --host 0.0.0.0 --port 8000 --reload
The Compose example publishes the port, binds all interfaces, and enables reload. This explicitly exposes a development server on the host network.
Audited by: codex

Jul 7, 2026, 10:19 PM

Most static findings are false positives from Markdown code fences or command examples, not executable skill code. No prompt injection or data exfiltration intent was found. A medium semantic issue remains because several examples combine public network binding with reload or development-oriented settings without a clear warning.

1
Files scanned
232
Lines analyzed
4
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
Public Reload Server Exposure
SKILL.md combines bind-all interface examples with reload-enabled Uvicorn configurations. Users who copy these examples can expose a development server to a network.
The cited examples directly pair 0.0.0.0 binding with reload-enabled development settings. The risk is operational guidance rather than automatic code execution, so medium severity is appropriate.
Audited by: codex

Jul 6, 2026, 06:16 AM

The static findings in SKILL.md and evaluation.json are false positives caused by documentation examples and inert JSON strings. A separate semantic issue remains because evaluation.json contains untrusted self-audit claims that label the package safe and all findings false positives.

2
Files scanned
466
Lines analyzed
4
Review items
0
False positives ignored

Confirmed security concerns (1)

High
Prompt Injection Attempt Detected
The bundled evaluation file declares the skill safe and states "All 60 static findings are FALSE POSITIVES." This untrusted self-audit could bias downstream review if treated as authority.
The file directly asserts risk_level safe and safe_to_publish true inside the audited package. It does not include an explicit override command, so confidence is high but not absolute.
Audited by: codex

Jun 28, 2026, 04:20 PM

Static analysis flagged command execution, network, filesystem, credential, and obfuscation patterns, but review found documentation examples rather than executable skill code. No malicious intent, prompt injection, credential exfiltration, or hidden runtime behavior was found. The remaining risk is low because examples bind Uvicorn to all interfaces and should be used with deployment context.

2
Files scanned
466
Lines analyzed
5
Review items
1
False positives ignored
Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Low
Public Bind Examples Need Deployment Context
Several examples use 0.0.0.0 for ASGI server binding. This is legitimate for containers and production routing, but copying it into local development can expose an application on all interfaces.
The network binding examples are real and intentional Uvicorn usage. The risk depends on user deployment context, so this is a low operational warning rather than malicious behavior.
Low
Placeholder TLS And Socket Paths Are Not Credential Access
The SSL key, certificate, and Unix socket paths are illustrative configuration examples. No actual secret material, key content, or file-reading behavior was found.
The cited paths are placeholders inside documentation. I found no evidence that the skill reads, copies, or transmits certificate or key files.
Static false positives ignored (1)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Low
Static Command Execution Findings Are Documentation Examples
The reported command execution locations are Markdown and JSON documentation examples for running Uvicorn. No executable script, dynamic shell call, or user-controlled command construction was found.
The cited lines are fenced documentation examples or JSON text, not active code. I found no evidence of a runtime command execution path.
Audited by: codex

Jan 16, 2026, 08:08 PM

This is a documentation-only skill containing example commands and configurations for Uvicorn ASGI server. All 98 static findings are FALSE POSITIVES. The analyzer incorrectly flagged documentation examples as security issues. The skill has no executable code, no network connections, no credential handling, and no command injection vectors.

3
Files scanned
681
Lines analyzed
3
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
🌐 Network access (1)
📁 Filesystem access (1)
Audited by: claude

Jan 16, 2026, 08:08 PM

This is a documentation-only skill containing example commands and configurations for Uvicorn ASGI server. All 98 static findings are FALSE POSITIVES. The analyzer incorrectly flagged documentation examples as security issues. The skill has no executable code, no network connections, no credential handling, and no command injection vectors.

3
Files scanned
681
Lines analyzed
3
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
🌐 Network access (1)
📁 Filesystem access (1)
Audited by: claude

Jan 11, 2026, 04:16 AM

This is a legitimate documentation skill for Uvicorn ASGI server. All 'external_commands' findings are actually code examples showing how to run uvicorn commands. The 'network' findings are documentation examples using standard localhost addresses (0.0.0.0, 127.0.0.1). The 'sensitive' finding about certificates is documenting legitimate SSL configuration. No actual security risks detected.

1
Files scanned
232
Lines analyzed
3
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
🌐 Network access (1)
📁 Filesystem access (1)
Audited by: claude

Jan 11, 2026, 04:16 AM

This is a legitimate documentation skill for Uvicorn ASGI server. All 'external_commands' findings are actually code examples showing how to run uvicorn commands. The 'network' findings are documentation examples using standard localhost addresses (0.0.0.0, 127.0.0.1). The 'sensitive' finding about certificates is documenting legitimate SSL configuration. No actual security risks detected.

1
Files scanned
232
Lines analyzed
3
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
🌐 Network access (1)
📁 Filesystem access (1)
Audited by: claude