Versioned security assessment

Report ID: SA-F967833C

4/17/2026, 8:43:56 AM

pexoai-agent security assessment v25

Skill Security Certification Report

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

Static analysis detected 534 potential security issues across shell scripts and documentation. After manual review, all findings are false positives from legitimate functionality: shell command examples in documentation (SETUP-CHECKLIST.md, TROUBLESHOOTING.md), standard API operations using curl/jq, config file access (~/.pexo/config) for credential storage, and network requests to official Pexo.ai endpoints. The skill is a legitimate video production tool with no malicious patterns 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

5 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 3 evidence locations

Filesystem access

May read or write local files.

Observed in 3 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 5 evidence locations

Capability review items (4)
Medium
Documentation Contains Shell Command Examples
SETUP-CHECKLIST.md and TROUBLESHOOTING.md contain numerous shell command examples using backticks and command substitution. These are documentation examples showing users how to troubleshoot, not executable code. No security risk.
Clear documentation pattern - files are Markdown references with code blocks, not executable scripts. Commands are instructional examples for users.
Low
Standard Shell Utilities for File Operations
Scripts use standard shell commands (stat, basename, jq, curl) for legitimate file operations, JSON parsing, and HTTP requests. All commands use fixed arguments or validated user input. No command injection vectors detected.
Standard utility usage patterns - no user input directly injected without sanitization. File paths validated before use.
Low
Config File Access for API Credentials
Script accesses ~/.pexo/config to read PEXO_API_KEY and PEXO_BASE_URL. This is the standard Unix pattern for storing user credentials. Config file is sourced with proper error handling.
Legitimate credential storage pattern following Unix conventions. File is user-owned with proper permissions documentation.
Low
Network Requests to Official Pexo.ai Endpoints
All hardcoded URLs point to official Pexo.ai services (pexo.ai, pexo-assets.oss-us-east-1.aliyuncs.com). No third-party or suspicious endpoints detected. Network activity is for legitimate API communication.
All URLs verified as official service endpoints. No data exfiltration patterns detected.

Risk findings

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

Confirmed security concerns (1)

RISK-001 Low
MD5 Hash Usage for Non-Security Purpose
One script uses MD5 hashing, but not for authentication or sensitive data. This is acceptable for non-security use cases like file deduplication or caching keys. No security impact.
MD5 used in utility context, not for security/crypto purposes. Acceptable use case.

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

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable