Versioned security assessment

Report ID: SA-697A452D

5/1/2026, 8:48:36 AM

pexoai-agent security assessment v39

Skill Security Certification Report

Audit History
Audit model: claude Historical report
Skill name
pexoai-agent
Version
v39
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

Low

1 confirmed security finding requires 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.

This is a legitimate video generation skill using shell scripts to interact with the Pexo AI video API. All static findings are false positives or standard API tool patterns. Shell script execution is expected for CLI-based API tools. Network calls go to the legitimate Pexo service (pexo.ai). Environment variable access (PEXO_API_KEY, PEXO_BASE_URL) is required for API authentication. No malicious intent 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

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 2 evidence locations

Filesystem access

May read or write local files.

Observed in 2 evidence locations

Env variables

May read values from the process environment.

Observed in 2 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 3 evidence locations

Capability review items (5)
High
scripts/pexo-project-create.sh:27scripts/pexo-upload.sh:33-89scripts/pexo-chat.sh:48-133
Shell Command Execution in Skill Scripts
Shell scripts use command substitution patterns (backticks, $()) for API operations. These are standard practices for CLI tools interacting with HTTP APIs. The scripts (pexo-project-create.sh, pexo-upload.sh, pexo-chat.sh) are the intended interface for the Pexo video service.
Shell script command execution is the expected design pattern for this skill type. No user input is injected into these commands.
Medium
scripts/_common.sh:21-22scripts/pexo-doctor.sh:82
API Key Access in Scripts
Scripts access PEXO_API_KEY environment variable for authentication. This is required for the Pexo API service and is stored in ~/.pexo/config file. The API key is used only for authenticating with pexo.ai.
API key access is legitimate for service authentication. No exfiltration observed.
Medium
scripts/_common.sh:7SKILL.md:30
Config File Access in Home Directory
Scripts read configuration from ~/.pexo/config. This is standard practice for API-based CLI tools.
Standard config file location for user-specific API credentials.
Medium
scripts/_common.sh:228-251SKILL.md:9-10
Network Requests to External API
Scripts make HTTP requests to pexo.ai API endpoints. This is the intended service the skill connects to.
Network calls are to the legitimate Pexo service domain, not unknown or suspicious endpoints.
Low
scripts/_common.sh:223-225
Temp File Creation in Scripts
Scripts create temporary files for HTTP response handling using mktemp. Standard practice for shell-based API clients.
mktemp is a standard safe practice for temporary file handling.

Risk findings

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

Confirmed security concerns (1)

RISK-001 Low
references/SETUP-CHECKLIST.md:9-15references/TROUBLESHOOTING.md:5-289
Documentation References to Shell Commands
Documentation files (SETUP-CHECKLIST.md, TROUBLESHOOTING.md) contain shell command examples. These are documentation for the setup process, not executable code.
Documentation examples are standard for setup guides.

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.

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