Versioned security assessment

Report ID: SA-68EF12B5

7/1/2026, 1:11:24 AM

hybrid-search-implementation security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
hybrid-search-implementation
Version
v6
Maintainer
wshobson
Coverage
1 Files scanned · 569 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

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.

Most static findings are false positives caused by Markdown code fences, search terminology, and resource links. The audit found a real SQL injection risk in the PostgreSQL template, where metadata keys are interpolated into SQL, so publication should wait for a safer example.

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

1 Files scanned · 569 Lines analyzed

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

Not recorded by this audit

Env variables

May read values from the process environment.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Not recorded by this audit

Risk findings

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

Confirmed security concerns (1)

RISK-001 High
SQL Injection Risk in PostgreSQL Filter Template
The PostgreSQL example appends filter metadata keys into a SQL WHERE clause and then interpolates that clause into conn.fetch. Values are parameterized, but keys are not validated or quoted, so untrusted filter names could alter the generated SQL.
The relevant code directly inserts metadata key names into SQL text before executing the query. This is a classic identifier injection issue, even though filter values use parameters.
Needs review findings (1)
REVIEW-001 Medium
Potential Elasticsearch Script Injection in Example Query
The Elasticsearch example inserts boost_vector into a script_score source string instead of passing it as a script parameter. The type hint says float, but copied code may receive untrusted runtime input.
The pattern is present in copyable code, but the parameter is annotated as a float and may be controlled only by trusted application code.

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 (3)
Low
Markdown Fences Misclassified as Shell Execution
The external command findings point to Markdown code fences and Python examples, not Ruby backtick shell execution. No executable shell command behavior is present in those locations.
The line-numbered evidence shows Markdown fences and section transitions. I did not find Ruby backtick execution at these locations.
Low
Credential and Weak Crypto Findings Are Vocabulary Matches
The sensitive, weak cryptography, and reconnaissance findings match words such as keyword, embedding, method, code, and index in search documentation. No certificates, private keys, hash routines, or system probing commands are shown.
The cited lines contain ordinary hybrid search terms and result ranking code. I did not find credential access, cryptographic operations, or host reconnaissance.
Low
Resource Links and Database Fetch Are Not Exfiltration
The network findings include a database fetch call inside an example and public documentation links. They do not send credentials or local data to an unauthorized endpoint.
The fetch call is asyncpg database access and the URLs are resource citations. I did not find evidence of credential exfiltration.

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