Versioned security assessment

Report ID: SA-730BD228

5/15/2026, 9:15:46 AM

pexoai-agent security assessment v51

Skill Security Certification Report

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

Evaluated 534 static analysis findings across 13 files (2110 lines). All 349 external_command detections are false positives: standard bash $(...) substitutions in legitimate shell scripts and backtick code blocks in markdown documentation. All 27 network detections reference the documented pexo.ai API and service URLs. All 79 filesystem detections involve the expected config directory (~/.pexo/config) and temp storage (~/.pexo/tmp), both documented in the skill's setup guide. All 25 env_access detections reference PEXO_API_KEY and PEXO_BASE_URL, which are required and documented configuration variables. No prompt injection, data exfiltration, or malicious intent found. Risk level set to medium due to the inherent credential handling and network communication required by the skill's purpose — not due to confirmed threats.

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.

Observed in 9 evidence locations

Network access

May connect to external services.

Observed in 8 evidence locations

Filesystem access

May read or write local files.

Observed in 7 evidence locations

Env variables

May read values from the process environment.

Observed in 6 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 7 evidence locations

Capability review items (3)
Medium
API Key Stored in Plaintext Config File
The skill requires PEXO_API_KEY to be stored in ~/.pexo/config as plaintext. While this is standard practice for CLI tools, it means the API key is readable by any process with filesystem access. The skill documents this clearly and uses a standard Unix hidden directory convention. Confidence: 0.55 — moderate concern given this is expected CLI behavior, not a flaw in the skill design.
Medium
Heuristic: Code Execution + Network + Credential Access Pattern
The static analyzer flagged a dangerous combination of shell command execution, network requests, and credential access. After manual evaluation, this pattern is confirmed as TRUE POSITIVE at the pattern level but FALSE POSITIVE for malicious intent. The skill is an API client that must execute commands, make network calls, and use credentials by design. All three capabilities are documented and transparent. Confidence: 0.85 — the pattern exists but is inherent to any API CLI tool; no malicious use was found.
Low
Hidden Directory Usage for Config and Temp Storage
The skill uses ~/.pexo/ for configuration and temporary file storage. This follows the standard Unix convention for per-user application data. Both the config path and temp directory are documented in the setup checklist. Confidence: 0.95 — expected and documented behavior.

Risk findings

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

Confirmed security concerns (1)

RISK-001 Low
Static Analyzer Over-Triggering on Markdown Code Blocks
The SETUP-CHECKLIST.md and TROUBLESHOOTING.md reference files contain extensive code examples in fenced markdown code blocks. The static analyzer flagged backtick characters and command patterns within these documentation examples as executable code. These are instructional examples, not live execution paths. Confidence: 0.98 — definitively false positive.

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
Hardcoded URLs in Documentation
Multiple markdown documentation files and shell scripts contain hardcoded URLs to pexo.ai and github.com. All URLs are legitimate service endpoints and documentation links for the Pexo platform. Confidence: 0.95 — definitively false positive for malicious intent; these are the expected service URLs.

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