Versioned security assessment

Report ID: SA-3A1246D0

5/25/2026, 9:32:20 AM

pexoai-agent security assessment v55

Skill Security Certification Report

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

Static analysis found 534 pattern matches across shell command execution, network calls, filesystem access, and env variable usage. All patterns are FALSE POSITIVES in context - they are legitimate operations for a shell-script-based video agent that wraps the Pexo API. The scripts execute curl commands to Pexo's official API endpoints, read a designated config file at ~/.pexo/config, and access required environment variables (PEXO_API_KEY, PEXO_BASE_URL). The associated heuristic detection of code-execution-plus-credential-access is expected behavior for an API-wrapping tool. The skill uses a mask_secret function to safely display API keys in diagnostic output. Risk level set to MEDIUM because the combination of external commands, network access, filesystem reads, and credential access creates a legitimate risk profile that users should understand, even though no malicious intent or data exfiltration patterns were 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

0 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 15 evidence locations

Filesystem access

May read or write local files.

Observed in 17 evidence locations

Env variables

May read values from the process environment.

Observed in 14 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 19 evidence locations

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 (10)
Medium
External command execution in shell scripts
FALSE POSITIVE: Shell command substitution patterns ($(...) and backtick) detected in .sh scripts and markdown docs. These are expected in executable shell scripts that form the skill's core functionality. Commands are curl (to Pexo API), jq (JSON parsing), and standard file utilities. No unvalidated user input is injected into command strings, so no command injection risk.
All shell command executions are within executable scripts using standard patterns. Command arguments are hardcoded or derived from controlled API responses, not from untrusted user input.
Medium
Hidden file in home directory
FALSE POSITIVE: References to ~/.pexo/config and similar dot-files are the designated configuration mechanism documented in the skill's requirements section. Reading a config file from the home directory is standard and expected behavior for CLI tools.
The config file path is a documented requirement of the skill. The pattern ~/.pexo/config is the explicit configuration mechanism, not an attempt to access arbitrary hidden files.
Medium
Weak cryptographic algorithm references
FALSE POSITIVE: References to 'sk-' prefix in API key documentation and usage examples are standard API key format descriptions, not implementations of weak cryptographic algorithms. The scanner pattern-matched the string 'sk-' as a cryptographic reference.
Only documentation and API key format validation are present. No actual cryptographic operations are performed in this codebase.
Medium
Environmental variable access for API keys
FALSE POSITIVE: PEXO_API_KEY and PEXO_BASE_URL are required configuration variables explicitly documented in the skill manifest. The skill needs these environment variables to authenticate with the Pexo video creation API. The diagnostic script masks the key value in output using mask_secret().
Env access is explicitly declared in the skill's requires block and is necessary for the skill to function. The diagnostic script takes care to mask the secret value in user-facing output.
Medium
Dangerous combination pattern: code execution, network, credential access
FALSE POSITIVE - Heuristic: The combination of external commands + network access + credential access is expected for an API-wrapping CLI tool. This skill runs shell scripts that use curl to make authenticated requests to Pexo's official API (pexo.ai). This is a legitimate architecture pattern for API-integrated tools, not malicious behavior.
All network requests target pexo.ai domains. Credentials are used only for Bearer auth headers. No external or unknown destinations are contacted. Pattern is standard for API-wrapping tools.
Low
Hardcoded URLs in documentation
FALSE POSITIVE: URLs hardcoded in SKILL.md and reference docs point to pexo.ai, the legitimate service domain. These are documentation links for user guidance (setup guide, project page, help center).
All URLs point to pexo.ai domains and are used as documentation links or API base URLs. No suspicious or unknown destinations detected.
Low
System reconnaissance commands
FALSE POSITIVE: Commands like uname, which, and file --version are used in the pexo-doctor.sh diagnostic script to verify system requirements. These are legitimate environment checks, not reconnaissance.
System information commands are used exclusively in a diagnostic tool that checks prerequisites. No exfiltration of system information occurs.
Low
Windows SAM database reference
FALSE POSITIVE: Static scanner misidentified content at SKILL.md:43 as a Windows SAM database reference. The actual content at that location is the language rule instruction: 'You MUST reply to the user in the SAME language they use.'
Line 43 contains a language instruction, not a reference to any system security database. Clear scanner false positive.
Low
Temp file creation in shell scripts
FALSE POSITIVE: mktemp is used in shell scripts to create temporary files for storing API response bodies and HTTP headers. Temp files are cleaned up with rm -f after processing. This is a standard pattern in shell scripting.
All temp files are created with mktemp and cleaned up in the same function. No sensitive data is written to temp files beyond API response payloads.
Low
Temp directory access
FALSE POSITIVE: The pexo_tmp_dir function uses ~/.pexo/tmp as a configurable temp directory. This is documented behavior within the skill's own config directory. No access to system /tmp or other temp locations occurs.
The temp directory path is configurable via PEXO_TMP_DIR and defaults to a subdirectory under the skill's own config directory. This is a standard sandboxing pattern.

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