Versioned security assessment

Report ID: SA-E69F5F48

6/28/2026, 1:21:24 PM

database security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
database
Version
v6
Maintainer
Azeem-2
Coverage
2 Files scanned · 881 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

2 confirmed security findings require 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.

The static high-risk results are mostly false positives from Markdown code fences, SQL text, and method names such as execute. No prompt injection, network exfiltration, install hook, or malicious runtime behavior was found, but database URL handling and raw SQL examples need publication 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

2 Files scanned · 881 Lines analyzed

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

Network access

May connect to external services.

Not recorded by this audit

Filesystem access

May read or write local files.

Not recorded by this audit

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

Risk findings

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

Confirmed security concerns (2)

RISK-001 Medium
Database Connection String Handling in Examples
TRUE_POSITIVE: The examples read DATABASE_URL and include a fallback database URL with placeholder credentials. This is legitimate guidance, but users who copy it unchanged could expose credentials or connect to an unintended database.
The environment variable and connection string are directly present in the documented code. The impact is moderate because this is Markdown guidance, not executable skill code.
RISK-002 Low
Local SQLite File Path Example
TRUE_POSITIVE: The development example uses a local SQLite database file path. This is normal for development, but copied production code should avoid placing database files in unsafe working directories.
The SQLite file path is explicitly present. The risk is low because it is labeled as development configuration and does not access files by itself.
Needs review findings (1)
REVIEW-001 Medium
Raw SQL Diagnostic Query Example
NEEDS_REVIEW: The performance section shows raw SQL passed to db.execute for PostgreSQL statistics. The query is fixed and not exfiltration, but production users should use bound parameters, SQLAlchemy text objects, and least-privilege monitoring roles.
The raw SQL execution pattern is visible and relevant to database security. It is not clearly exploitable because the shown query is static and the threshold is passed separately.

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
Weak Cryptography Static Hits Dismissed
FALSE_POSITIVE: The weak cryptography alerts point to Markdown metadata, SQL terms, and audit text rather than cryptographic code. No evidence found of weak hash algorithms, cipher use, password hashing, or token generation.
The referenced files are documentation and generated audit output, not crypto implementations. The reviewed context contains database terms and Markdown content only.
Low
Process Execution Static Hits Dismissed
FALSE_POSITIVE: The Python exec and process execution alerts map to database method names, query execution examples, and Markdown code fences. No evidence found of Python exec(), subprocess, shell commands, backtick shell execution, or command injection.
The suspicious tokens are part of database API examples. There is no shell or interpreter invocation in the reviewed Markdown.
Low
System Reconnaissance Static Hits Dismissed
FALSE_POSITIVE: The system reconnaissance alerts are located in ordinary database examples. No evidence found of host enumeration, process listing, credential discovery, or environment dumping.
The cited lines occur inside repository and query examples. The semantic context is database access logic, not machine reconnaissance.

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