📦

Audit History

dbt-transformation-patterns - 8 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v8 LatestJul 7, 2026, 07:13 AM No confirmed findings0No capability change
v7 Jul 7, 2026, 07:13 AM No confirmed findings0No capability change
v6 Jun 30, 2026, 10:41 PM No confirmed findings0No capability change
v5 Jun 30, 2026, 10:41 PM No confirmed findings0No capability change
v4 Jan 17, 2026, 08:06 AM No confirmed findings0No capability change
v3 Jan 17, 2026, 08:06 AM No confirmed findings0Network accessExternal commands
v2 Jan 4, 2026, 05:04 PM No confirmed findings0No capability change
v1 Jan 4, 2026, 05:04 PM No confirmed findings0Baseline

Jul 7, 2026, 07:13 AM

I reviewed SKILL.md and found no evidence of malicious intent, prompt injection, data exfiltration, or executable payloads. All static findings are false positives caused by Markdown fences, inline code, dbt SQL/YAML examples, standard dbt CLI examples, and documentation URLs. No semantic security findings were identified.

1
Files scanned
562
Lines analyzed
2
Review items
0
False positives ignored
Audited by: codex

Jul 7, 2026, 07:13 AM

I reviewed SKILL.md and found no evidence of malicious intent, prompt injection, data exfiltration, or executable payloads. All static findings are false positives caused by Markdown fences, inline code, dbt SQL/YAML examples, standard dbt CLI examples, and documentation URLs. No semantic security findings were identified.

1
Files scanned
562
Lines analyzed
2
Review items
0
False positives ignored
Audited by: codex

Jun 30, 2026, 10:41 PM

Static analysis flagged Markdown backticks, dbt model names, and documentation links as execution, cryptography, reconnaissance, and network risks. Review found a single Markdown guide with dbt examples, user-run CLI commands, and official resource links; no hidden execution, exfiltration, prompt injection, or malicious intent was found.

1
Files scanned
562
Lines analyzed
2
Review items
4
False positives ignored
Static false positives ignored (4)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Low
Markdown Backticks Misclassified as Shell Execution
The external command alerts point to Markdown fences, inline code spans, SQL examples, YAML examples, and dbt CLI examples. The file is documentation and does not execute these commands automatically.
The flagged content is inside Markdown code fences or inline formatting in SKILL.md. No runnable script, shell interpolation, or automatic command execution path exists in the skill.
Low
Weak Cryptography Alerts Are Text Matches
The weak cryptography alerts match ordinary dbt documentation text such as model descriptions, customer identifiers, documentation guidance, and dbt utility examples. No cryptographic API or hashing implementation is present.
The reviewed lines contain prose, YAML descriptions, and dbt model names. I found no MD5, SHA1, DES, RC4, or similar cryptographic operation in the file.
Low
Documentation Links Are Benign External References
The hardcoded URLs are resource links to dbt documentation, dbt best practices, dbt-utils, and dbt Discourse. They are not fetched by the skill and do not transmit local data.
The URLs appear only in a Resources section as Markdown links. There is no network client, webhook, credential handling, or data upload logic.
Low
Reconnaissance Alerts Are SQL and dbt Terms
The system reconnaissance alerts are caused by benign terms such as id fields, joins, model names, and dbt commands. They do not inspect the host system or collect environment details.
The flagged lines are schema examples and SQL joins in a dbt tutorial. I found no host probing, directory enumeration, process inspection, or secret discovery behavior.

Risk Factors

⚙️ External commands (1)
🌐 Network access (1)
Audited by: codex

Jun 30, 2026, 10:41 PM

Static analysis flagged Markdown backticks, dbt model names, and documentation links as execution, cryptography, reconnaissance, and network risks. Review found a single Markdown guide with dbt examples, user-run CLI commands, and official resource links; no hidden execution, exfiltration, prompt injection, or malicious intent was found.

1
Files scanned
562
Lines analyzed
2
Review items
4
False positives ignored
Static false positives ignored (4)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Low
Markdown Backticks Misclassified as Shell Execution
The external command alerts point to Markdown fences, inline code spans, SQL examples, YAML examples, and dbt CLI examples. The file is documentation and does not execute these commands automatically.
The flagged content is inside Markdown code fences or inline formatting in SKILL.md. No runnable script, shell interpolation, or automatic command execution path exists in the skill.
Low
Weak Cryptography Alerts Are Text Matches
The weak cryptography alerts match ordinary dbt documentation text such as model descriptions, customer identifiers, documentation guidance, and dbt utility examples. No cryptographic API or hashing implementation is present.
The reviewed lines contain prose, YAML descriptions, and dbt model names. I found no MD5, SHA1, DES, RC4, or similar cryptographic operation in the file.
Low
Documentation Links Are Benign External References
The hardcoded URLs are resource links to dbt documentation, dbt best practices, dbt-utils, and dbt Discourse. They are not fetched by the skill and do not transmit local data.
The URLs appear only in a Resources section as Markdown links. There is no network client, webhook, credential handling, or data upload logic.
Low
Reconnaissance Alerts Are SQL and dbt Terms
The system reconnaissance alerts are caused by benign terms such as id fields, joins, model names, and dbt commands. They do not inspect the host system or collect environment details.
The flagged lines are schema examples and SQL joins in a dbt tutorial. I found no host probing, directory enumeration, process inspection, or secret discovery behavior.

Risk Factors

⚙️ External commands (1)
🌐 Network access (1)
Audited by: codex

Jan 17, 2026, 08:06 AM

Pure documentation skill containing only SQL and YAML examples for dbt patterns. The static analyzer produced false positives: YAML frontmatter markers were flagged as shell backticks, Jinja2 template syntax was flagged as command execution, and normal dbt CLI commands were flagged as reconnaissance. All findings are dismissed. No executable code, network calls, file system access, or external command execution capabilities exist.

2
Files scanned
740
Lines analyzed
2
Review items
0
False positives ignored
Audited by: claude

Jan 17, 2026, 08:06 AM

Pure documentation skill containing only SQL and YAML examples for dbt patterns. The static analyzer produced false positives: YAML frontmatter markers were flagged as shell backticks, Jinja2 template syntax was flagged as command execution, and normal dbt CLI commands were flagged as reconnaissance. All findings are dismissed. No executable code, network calls, file system access, or external command execution capabilities exist.

2
Files scanned
740
Lines analyzed
2
Review items
0
False positives ignored
Audited by: claude

Jan 4, 2026, 05:04 PM

Pure documentation skill containing only SQL and YAML examples for dbt patterns. No executable code, network calls, file system access, or external command execution capabilities. Contains only static educational content about data build tool practices.

4
Files scanned
834
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude

Jan 4, 2026, 05:04 PM

Pure documentation skill containing only SQL and YAML examples for dbt patterns. No executable code, network calls, file system access, or external command execution capabilities. Contains only static educational content about data build tool practices.

4
Files scanned
834
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude