Security Audit

zyla-api-hub-skill

github.com/openclaw/skills

AI SkillCommit 13146e6a3d46

CAUTION

Scanned about 2 months ago

Critical

Immediate action required

High

Priority fixes suggested

Medium

Best practices review

Low

Acknowledged / Tracked

Trust Assessment

zyla-api-hub-skill received a trust score of 57/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.

SkillShield's automated analysis identified 3 findings: 1 critical, 0 high, 2 medium, and 0 low severity. Key findings include Network egress to untrusted endpoints, Unpinned npm dependency version, Unpinned Dependency Versions.

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 14, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.

Layer Breakdown

Manifest Analysis

70%

Static Code Analysis

100%

Dependency Graph

93%

LLM Behavioral Safety

93%

Behavioral Risk Signals

Network Access

1 finding

Security Findings3

Severity	Finding	Layer	Location
CRITICAL	Network egress to untrusted endpoints HTTP request to raw IP address Review all outbound network calls. Remove connections to webhook collectors, paste sites, and raw IP addresses. Legitimate API calls should use well-known service domains.	Manifest	skills/alebrega/zyla-api-hub-skill/plugin/index.ts:223
MEDIUM	Unpinned npm dependency version Dependency 'tsx' is not pinned to an exact version ('^4'). Pin dependencies to exact versions to reduce drift and supply-chain risk.	Dependencies	skills/alebrega/zyla-api-hub-skill/package.json
MEDIUM	Unpinned Dependency Versions The 'tsx' and 'open' dependencies are specified with caret (^) ranges in package.json and package-lock.json, allowing for minor and patch version updates. This introduces a supply chain risk, as a malicious update to a dependency could be automatically pulled in without explicit review, potentially introducing vulnerabilities. Pin dependencies to exact versions (e.g., "tsx": "4.x.x", "open": "10.x.x") or use a lockfile (which is present, but exact pinning adds an extra layer of control) to ensure deterministic builds and prevent unexpected changes from upstream packages. Regularly audit and update dependencies.	LLM	package.json:19

Scan History

Embed Code

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