Versioned security assessment

Report ID: SA-E0816CB0

6/30/2026, 11:29:59 AM

qryma-search security assessment v5

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
qryma-search
Version
v5
Maintainer
qryma-ai
Source
github.com/qryma-ai/skills/tree/main/
Coverage
12 Files scanned · 770 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

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 found many env, network, filesystem, and external command indicators. Review confirms a legitimate community web search client, not malicious code, but it sends queries and an API key to an external endpoint and reads local credential files. The critical heuristic is dismissed as a false positive for intent, with publication allowed only with clear credential and network warnings.

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

12 Files scanned · 770 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 9 evidence locations

Filesystem access

May read or write local files.

Observed in 6 evidence locations

Env variables

May read values from the process environment.

Observed in 10 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 5 evidence locations

Capability review items (4)
Medium
scripts/search_core.py:77-79scripts/search_core.py:103-119scripts/search_core.py:123
Credential-Bearing Network Request
The search client posts user queries to the configured endpoint and includes the Qryma API key in the X-Api-Key header. This is expected for the skill, but users must understand that query text and credentials leave the local environment.
The code directly builds a POST request to self.endpoint and attaches self.api_key as X-Api-Key. The behavior is semantically legitimate for a search API client, so it is medium rather than high risk.
Medium
scripts/search_core.py:47-66scripts/search_core.py:71scripts/search_core.py:112-119
Configurable Endpoint Can Receive API Key and Queries
The endpoint can be loaded from QRYMA_ENDPOINT or a .env file before network requests are made. If configuration is tampered with, the API key and search queries could be sent to an unintended server.
Endpoint override behavior is explicit in code and is later used as the request target. Legitimate customization is possible, but the trust boundary is real.
Medium
scripts/search_core.py:29-40scripts/search_core.py:55-66
Local Credential File Reads
The skill reads QRYMA_API_KEY and QRYMA_ENDPOINT from ~/.qryma/.env or .env. This is normal configuration handling, but it accesses hidden home-directory files and local environment files.
The file paths and parsing logic are directly visible. The reads are scoped to Qryma variables, which lowers risk but still requires disclosure.
Low
README.md:10-18README.md:35-43SKILL.md:17-29SKILL.md:61-68
Shell Command Detections Are Documentation Examples
Static analysis flagged shell-like command blocks in README.md and SKILL.md. These are installation and usage examples, not commands executed automatically by the skill.
The suspicious text appears inside Markdown fenced examples. No evidence found that the skill executes these command strings automatically.

Risk findings

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

Confirmed security concerns (1)

RISK-001 Medium
README.md:21-30SKILL.md:46-55
Documentation Encourages Sharing API Key With Assistant
The documentation tells users to ask an AI assistant to configure QRYMA_API_KEY and includes example prompts containing the key placeholder. This can train users to paste real credentials into chat.
The wording and examples are explicit. The risk is documentation-driven credential exposure, not hidden code execution.

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: codex

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 (2)
Low
manifest.json:5manifest.json:32-39skill.json:5-7SKILL.md:33-42
Weak Cryptography Detections Are False Positives
Static analysis reported weak cryptographic algorithms across metadata and documentation. Review found descriptions, options, and Markdown format references, with no cryptographic implementation in the cited files.
The cited lines contain metadata, argument descriptions, or output format text. No evidence found of MD5, SHA1, or another weak cryptographic primitive being used.
Low
scripts/search_core.py:14scripts/search_core.py:71manifest.json:7package.json:22-24
Hardcoded URLs Are Expected Service and Documentation Links
Hardcoded URL findings point to the Qryma service endpoint, project homepage, repository, or language documentation. These are expected for a web search integration.
The URLs match the advertised service or supporting documentation. No evidence found of unrelated exfiltration domains.

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