Versioned security assessment

Report ID: SA-EAEF8608

5/7/2026, 9:03:48 AM

pexoai-agent security assessment v45

Skill Security Certification Report

Audit History
Audit model: claude Historical report
Skill name
pexoai-agent
Version
v45
Maintainer
pexoai
Source
github.com/pexoai/pexo-skills/tree/main/skills/pexo-agent/
Coverage
13 Files scanned · 2,110 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

3 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.

The Pexo AI Video Agent is a legitimate video generation CLI tool. Static analysis detected 534 patterns including shell command usage, network access, and credential handling. All findings are legitimate API client behavior - the tool requires PEXO_API_KEY authentication and makes API calls to pexo.ai for video generation. The CRITICAL heuristic finding about dangerous combinations is a false positive - the combination of code execution, network access, and credential access is expected for any external API client. No malicious behavior detected.

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

13 Files scanned · 2,110 Lines analyzed

3 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 2 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 1 evidence location

External commands

May invoke commands or programs outside the Skill.

Observed in 1 evidence location

Risk findings

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

Confirmed security concerns (3)

RISK-001 Medium
references/SETUP-CHECKLIST.md:1-92references/TROUBLESHOOTING.md:1-290
Shell Commands in Documentation
Documentation files (SETUP-CHECKLIST.md, TROUBLESHOOTING.md) contain shell command examples with backtick syntax shown for user reference. These are documentation examples, not executable code. The actual shell scripts use hardcoded commands without user input injection vectors.
The backtick syntax appears in markdown documentation as examples. Actual shell scripts use hardcoded commands with no user input passed to shell execution.
RISK-002 Medium
scripts/_common.sh:3-33
Config File Access for API Credentials
The skill accesses ~/.pexo/config to read PEXO_API_KEY and PEXO_BASE_URL. This is legitimate credential handling for an API client tool. The skill does not exfiltrate credentials - it reads local config to authenticate with the Pexo API.
Standard credential loading pattern for CLI API clients. Credentials are read from local config and used only for authentication with the documented Pexo service.
RISK-003 Low
scripts/pexo-doctor.sh:1-201
System Reconnaissance in Doctor Script
The pexo-doctor.sh script performs system checks (OS type, installed tools, network connectivity). This is legitimate diagnostic functionality for a CLI tool to verify prerequisites before API usage.
Diagnostic scripts commonly check system requirements. This is expected for a developer tool that requires specific runtime dependencies.

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: claude

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 (2)
Critical
SKILL.md:1-332scripts/_common.sh:1-431
False Positive: Heuristic Detection of Dangerous Combination
The static analyzer flagged '[HEURISTIC] DANGEROUS COMBINATION: Code execution + Network + Credential access' as CRITICAL. This is a false positive - the combination of shell commands, network API calls, and API key authentication is expected behavior for a legitimate API client CLI tool. All network calls go to the official Pexo API service at pexo.ai. No malicious behavior detected.
The heuristic flagged the legitimate combination of API client patterns. The SKILL.md shows this is a video generation tool requiring PEXO_API_KEY authentication to call the pexo.ai API service - this is standard API client behavior.
Critical
SKILL.md:43
False Positive: Windows SAM Database Detection
The static analyzer flagged 'Windows SAM database' at SKILL.md:43 as CRITICAL sensitive data access. This is a false positive - the actual line contains 'You MUST reply to the user in the SAME language they use' where the word 'SAME' or 'MUST' triggered an incorrect SAM (Security Account Manager) database heuristic.
Line 43 contains language instruction text with no connection to Windows system files. The heuristic incorrectly matched partial strings.

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