Versioned security assessment

Report ID: SA-6A0F7FBC

4/27/2026, 9:00:58 AM

pexoai-agent security assessment v35

Skill Security Certification Report

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

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

This is a legitimate video generation API client for pexo.ai. Static analysis detected 534 potential issues, but evaluation reveals these are mostly documentation examples (showing users what commands to run) and standard shell scripting patterns for API operations. The skill makes network calls only to pexo.ai, uses environment variables only for its own API credentials (PEXO_API_KEY), and performs standard file operations for configuration and asset uploads. No malicious behavior, data exfiltration, or command injection vulnerabilities were found. All findings are consistent with expected behavior for a video API client tool.

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

4 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 8 evidence locations

Filesystem access

May read or write local files.

Observed in 8 evidence locations

Env variables

May read values from the process environment.

Observed in 4 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 12 evidence locations

Capability review items (2)
Medium
scripts/_common.sh:223-414scripts/pexo-chat.sh:48-155scripts/pexo-upload.sh:33-107
Shell Command Substitution in Scripts
Scripts use $(command) substitution for legitimate API operations: extracting asset IDs, reading config files, file metadata. VERDICT: FALSE POSITIVE - Standard shell scripting patterns for a legitimate API client.
Command substitutions in scripts are used for: mktemp (temp files), cat (reading response files), jq (JSON parsing), basename/stat (file operations). These are standard patterns for API client operations.
Low
references/SETUP-CHECKLIST.md:10-14SKILL.md:30-35
API Key Configuration in User Config File
Skill requires PEXO_API_KEY to be stored in ~/.pexo/config. This is standard API client credential management. VERDICT: LOW RISK - User-managed credentials with clear documentation.
Config file storage for API keys is standard practice. Documentation clearly instructs users to keep credentials secure. Skill does not transmit credentials to third parties.

Risk findings

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

Confirmed security concerns (2)

RISK-001 Medium
references/SETUP-CHECKLIST.md:9-91references/TROUBLESHOOTING.md:5-288
Documentation Examples Flagged as Commands
Static scanner flagged command examples in documentation files (SETUP-CHECKLIST.md, TROUBLESHOOTING.md) as shell execution. These are documentation showing users what commands to run, not actual code execution points. VERDICT: FALSE POSITIVE - These are user-facing documentation examples.
Documentation files contain markdown code blocks showing users what commands to run for setup and troubleshooting. The backtick notation in markdown is documentation syntax, not actual shell execution.
RISK-002 Low
references/TROUBLESHOOTING.md:87
MD5 Referenced in Documentation
Static scanner flagged 'weak cryptographic algorithm' at references/TROUBLESHOOTING.md:87 referencing md5. This is documentation showing users how to verify file checksums, not actual cryptographic use. VERDICT: FALSE POSITIVE - Non-security use of MD5 for file integrity checks.
MD5 is documented as a file checksum utility (md5 file.mp4), not for cryptographic security. This is standard documentation for verifying downloaded file integrity.

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