πŸ“¦

Audit History

conversion-signal-qa - 7 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v7 LatestJul 26, 2026, 10:07 AM No confirmed findings0No capability change
v6 Jul 26, 2026, 10:07 AM No confirmed findings0No capability change
v5 Jul 13, 2026, 12:44 PM No confirmed findings0No capability change
v4 Jul 13, 2026, 12:44 PM No confirmed findings0No capability change
v3 Jul 12, 2026, 11:46 AM No confirmed findings0No capability change
v2 Jul 6, 2026, 04:25 PM No confirmed findings0No capability change
v1 Jul 4, 2026, 04:05 PM 1 confirmed0Baseline

Jul 26, 2026, 10:07 AM

All 39 static findings are false positives caused by Markdown formatting, relative documentation links, and marketing terminology. The skill contains no executable commands, network requests, path traversal behavior, prompt-injection language, or evidence of data exfiltration. It explicitly treats pasted exports as untrusted and requires consent before saving results.

3
Files scanned
167
Lines analyzed
3
Review items
0
False positives ignored
Audited by: claude

Jul 26, 2026, 10:07 AM

All 39 static findings are false positives caused by Markdown formatting, relative documentation links, and marketing terminology. The skill contains no executable commands, network requests, path traversal behavior, prompt-injection language, or evidence of data exfiltration. It explicitly treats pasted exports as untrusted and requires consent before saving results.

3
Files scanned
167
Lines analyzed
3
Review items
0
False positives ignored
Audited by: claude

Jul 13, 2026, 12:44 PM

All 39 static findings are false positives caused by Markdown links, code fences, inline code, slash-separated labels, or repository metadata. The skill contains no executable commands, network requests, path traversal operations, reconnaissance behavior, or prompt injection.

3
Files scanned
167
Lines analyzed
3
Review items
0
False positives ignored
Audited by: codex

Jul 13, 2026, 12:44 PM

All 39 static findings are false positives caused by Markdown links, code fences, inline code, slash-separated labels, or repository metadata. The skill contains no executable commands, network requests, path traversal operations, reconnaissance behavior, or prompt injection.

3
Files scanned
167
Lines analyzed
3
Review items
0
False positives ignored
Audited by: codex

Jul 12, 2026, 11:46 AM

All 39 static findings are false positives caused by Markdown formatting, relative documentation links, marketing terminology, and homepage metadata. The skill contains no executable code, network request, prompt injection, or unsafe path handling, and consent is required before saving results.

3
Files scanned
167
Lines analyzed
3
Review items
0
False positives ignored
Audited by: codex

Jul 6, 2026, 04:25 PM

No confirmed malicious behavior was found. Static findings are false positives caused by Markdown links, fenced prompt examples, metadata URLs, and marketing analytics terms.

3
Files scanned
167
Lines analyzed
3
Review items
0
False positives ignored
Audited by: codex

Jul 4, 2026, 04:05 PM

The static findings are false positives caused by Markdown links, fenced prompt examples, inline-code formatting, and repository metadata URLs. No prompt-injection attempt, hidden command execution, runtime network call, or malicious exfiltration intent was found. One medium semantic issue remains: the optional memory save path uses a <topic> filename placeholder without an explicit sanitization rule.

3
Files scanned
167
Lines analyzed
4
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
Unsanitized Memory Filename Placeholder
The skill tells the agent to write results to memory/ad/conversion-signal-qa/YYYY-MM-DD-<topic>.md after user approval. It does not explicitly require the topic segment to be slugified or stripped of path separators. A malicious or accidental topic value could cause writes outside the intended folder if the host agent uses it literally.
Line 67 contains a user-facing <topic> placeholder inside a write path, and no nearby instruction requires sanitization. The skill also requires user approval before writing, so the issue is a bounded path-handling risk rather than clear malicious intent.
Audited by: codex