Versioned security assessment

Report ID: SA-E4ABF994

5/5/2026, 8:55:24 AM

pexoai-agent security assessment v43

Skill Security Certification Report

Audit History

Audit model: claude Historical report

Skill name: pexoai-agent
Version: v43
Maintainer: pexoai
Source: github.com/pexoai/pexo-skills/tree/main/skills/pexo-agent/
Coverage: 13 Files scanned · 2,110 Lines analyzed
Policy version: Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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.

Skill executes bash scripts to interact with Pexo AI video API. Static scanner detected external commands and env access patterns typical of API client scripts. Evaluation confirms these patterns are legitimate API client operations: scripts execute hardcoded commands with validated inputs, access config file for API credentials, and make network requests to Pexo API endpoints. Hidden file access (e.g., ~/.pexo/config) is standard practice for config management. No user input injection vectors found. High count of findings is due to documentation files (SETUP-CHECKLIST.md, TROUBLESHOOTING.md) containing shell examples, not executable code.

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.

Source

Binding unavailable
Artifact

Identity incomplete
Audit

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

Observed in 3 evidence locations

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

Capability review items (6)

High

SKILL.md:90 SKILL.md:261 scripts/pexo-project-get.sh:137 scripts/pexo-project-get.sh:144

Weak Cryptographic Algorithm Usage (MD5)

MD5 hash functions used in shell scripts for temporary file naming. MD5 is cryptographically weak but used here for non-security purposes (temp file generation), not authentication or integrity verification.

MD5 usage found but only for temp file naming, not security-critical operations. Low risk in this context.

Medium

scripts/_common.sh:223-225 scripts/pexo-chat.sh:48 scripts/pexo-upload.sh:52-55

Shell Command Execution in Scripts

Scripts use bash command substitution $(...) for API interactions, file operations, and system diagnostics. Commands are hardcoded with no user input injection vectors.

Command substitution patterns are standard for API client scripts. All commands use validated inputs, no user-controlled command concatenation.

Medium

scripts/_common.sh:3 scripts/pexo-asset-get.sh:13

Hidden Configuration File Access

Scripts read configuration from ~/.pexo/config. Standard practice for API client credentials storage, not malicious file access.

Config file access is standard for API client scripts. File path is hardcoded, not user-controlled.

Medium

scripts/_common.sh:21-22 scripts/pexo-doctor.sh:82 SKILL.md:13

Environment Variable Access for Credentials

Scripts read PEXO_API_KEY and PEXO_BASE_URL from environment or config file. Standard credential management pattern for API clients.

Credential access is legitimate API client pattern. No exfiltration detected - credentials only sent to Pexo API endpoints.

Medium

scripts/_common.sh:279 scripts/pexo-doctor.sh:81 SKILL.md:9-10

Network Requests to Hardcoded URLs

Scripts make HTTP requests to https://pexo.ai and related endpoints. Hardcoded URLs are expected for API clients.

Network requests go to legitimate Pexo API. No suspicious external endpoints detected.

Low

scripts/_common.sh:44 scripts/pexo-doctor.sh:32

Standard Device File Access

Scripts access /dev/null and standard streams. Normal shell scripting practice.

Standard file descriptors (/dev/null, stdin/stdout/stderr) are normal shell operations.

Risk findings

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

No confirmed security findings were recorded for this completed audit.

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 (1)

Low

references/SETUP-CHECKLIST.md:35 references/TROUBLESHOOTING.md:7

System Reconnaissance Patterns in Documentation

Documentation files contain shell commands checking system state (curl, jq availability). These are troubleshooting instructions for users, not malicious reconnaissance.

Commands are in documentation (TROUBLESHOOTING.md), not executable code. Standard diagnostic patterns for setup guides.

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