Security Audit

swiss-phone-directory

github.com/openclaw/skills

AI SkillCommit 13146e6a3d46

TRUSTED

Scanned about 2 months ago

Critical

Immediate action required

High

Priority fixes suggested

Medium

Best practices review

Low

Acknowledged / Tracked

Trust Assessment

swiss-phone-directory received a trust score of 93/100, placing it in the Trusted category. This skill has passed all critical security checks and demonstrates strong security practices.

SkillShield's automated analysis identified 2 findings: 0 critical, 0 high, 1 medium, and 0 low severity. Key findings include Suspicious import: urllib.request, API Key in URL Query Parameters.

The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.

Last analyzed on February 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.

Layer Breakdown

Manifest Analysis

100%

Static Code Analysis

93%

Dependency Graph

100%

LLM Behavioral Safety

100%

Behavioral Risk Signals

Network Access

2 findings

Excessive Permissions

2 findings

Security Findings2

Severity	Finding	Layer	Location
MEDIUM	Suspicious import: urllib.request Import of 'urllib.request' detected. This module provides network or low-level system access. Verify this import is necessary. Network and system modules in skill code may indicate data exfiltration.	Static	skills/xenofex7/swiss-phone-directory/searchch.py:10
INFO	API Key in URL Query Parameters The `SEARCHCH_API_KEY` is sent as a query parameter in the URL for API requests. While this is often dictated by the API's design (e.g., search.ch API), it is generally less secure than sending API keys in HTTP headers. This method can expose the key in server access logs, proxy logs, or browser history (if applicable), increasing the risk of accidental exposure. If the target API supports it, prefer sending API keys in HTTP Authorization headers (e.g., `Authorization: Bearer <key>`) rather than in URL query parameters. If the API strictly requires the key in the URL, ensure that all systems handling these URLs (e.g., web servers, proxies, logging systems) are configured to prevent logging or exposing the full URL with sensitive parameters.	LLM	searchch.py:56

Scan History

Embed Code

[![SkillShield](https://skillshield.io/api/v1/badge/7f486fc96b9c3500.svg)](https://skillshield.io/report/7f486fc96b9c3500)