Versioned security assessment

Report ID: SA-5AE7412A

6/30/2026, 2:59:14 PM

data-quality-frameworks security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
data-quality-frameworks
Version
v2
Maintainer
sickn33
Coverage
2 Files scanned · 615 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.

The high static score is driven by markdown examples, inline framework names, and documentation links rather than executable skill code. No malicious intent, prompt injection, credential exfiltration, or hidden automation was found. Minor risk remains because the playbook includes user-run setup commands and notification examples that may expose validation details if configured poorly.

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 · 615 Lines analyzed

1 item 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 4 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.

Observed in 30 evidence locations

Risk findings

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

Confirmed security concerns (1)

RISK-001 Low
Notification Example Could Expose Validation Details
The Great Expectations checkpoint example includes a Slack webhook placeholder for failure notifications. This is a legitimate pattern, but users should avoid sending sensitive row values or PII in validation alerts.
The notification pattern is explicit, but it uses an environment placeholder and does not hardcode a destination. Exposure depends on user configuration and validation result contents.

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
External Command Examples Are Documentation Only
Static analysis flagged shell-like content, but the reviewed lines are markdown examples for installing and initializing Great Expectations or opening the implementation playbook. These examples are not executed by the skill and do not contain dynamic command construction.
The flagged content appears inside markdown instructions and fenced examples. I found no executable script, hook, or user-input command injection path.
Low
Framework Syntax Misclassified as Security Indicators
The weak cryptography and reconnaissance flags map to ordinary data modeling terms such as primary key, foreign key, UUID format, timestamps, and dbt ref syntax. These are normal data quality concepts and not evidence of malware or system probing.
The reviewed context is schema and test documentation, not cryptographic or reconnaissance code. The terms are semantically tied to data contracts and dbt examples.
Low
Documentation Links Are Benign Network References
The hardcoded URLs are links to official documentation for Great Expectations, dbt, data contracts, and Soda Core. They are not fetched by code and do not transmit local data.
The URLs appear only in a markdown Resources section. I found no code path that requests these URLs or sends data to them.

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