Skills graphql Audit History
📦

Audit History

graphql - 5 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v5 LatestJul 24, 2026, 12:53 AM 1 confirmed0No capability change
v4 Jul 8, 2026, 12:09 PM No confirmed findings0Network accessEnv variables
v3 Jul 7, 2026, 01:28 AM No confirmed findings0External commands
v2 Jun 30, 2026, 04:52 PM No confirmed findings0No capability change
v1 Feb 25, 2026, 03:58 AM No confirmed findings0Baseline

Jul 24, 2026, 12:53 AM

All 40 static alerts are false positives caused by GraphQL templates, JavaScript interpolation, development configuration, and ordinary identifier checks. However, the subscription example trusts a client-supplied identity and lacks room authorization, which can expose events if copied into production.

1
Files scanned
1,077
Lines analyzed
4
Review items
0
False positives ignored

Confirmed security concerns (1)

High
Client-Supplied Subscription Identity
The example trusts userId from connectionParams and subscribes to arbitrary room topics without authentication or membership checks, enabling impersonation and unauthorized event access.
The context directly copies userId from client-controlled connection parameters, and the subscription filter checks only the requested roomId.
Audited by: codex

Jul 8, 2026, 12:09 PM

Reviewed 40 static findings in SKILL.md. They are false positives caused by JavaScript template literals, GraphQL examples, NODE_ENV checks, account lockout terminology, and normal GraphQL ID fields in documentation. No semantic evidence of prompt injection, data exfiltration intent, malware behavior, or unsafe execution was found.

1
Files scanned
1,077
Lines analyzed
3
Review items
0
False positives ignored
Audited by: codex

Jul 7, 2026, 01:28 AM

The only static finding is a false positive: line 68 uses Markdown backticks around related skill names, not shell execution. No prompt injection, exfiltration intent, or other semantic security issue was found in the reviewed SKILL.md.

1
Files scanned
69
Lines analyzed
1
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
Audited by: codex

Jun 30, 2026, 04:52 PM

The static analyzer reported shell backticks and weak cryptographic algorithm patterns, but review found no executable code, scripts, network calls, or cryptographic operations. The backticks are Markdown formatting on line 68, and the weak-crypto hits are text matches in GraphQL and design-related prose. No prompt injection or malicious intent was found.

1
Files scanned
69
Lines analyzed
0
Review items
2
False positives ignored
Static false positives ignored (2)

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
False Positive: Markdown Backticks Flagged as Shell Execution
The static analyzer reported Ruby or shell backtick execution at line 68. The line only uses Markdown inline code formatting for related skill names, so no command execution path is present.
The reviewed line contains only Markdown text and inline backticks around skill names. There is no script language context or executable command syntax.
Low
False Positive: Design Text Flagged as Weak Cryptography
The static analyzer reported weak cryptographic algorithm patterns on lines 3, 21, 33, and 62. These lines contain GraphQL description and schema design text, not cryptographic APIs or algorithm selection.
The flagged locations are natural-language GraphQL guidance and capability names. No hashing, encryption, or cryptographic implementation appears in the file.
No confirmed security findings were recorded for this completed audit.
Audited by: codex

Feb 25, 2026, 03:58 AM

This skill is a documentation file containing GraphQL best practices and patterns. Static analysis flagged false positives: line 69 references related skills (not shell execution), and lines 3, 22, 34, 63, 72 contain markdown content (not cryptographic code). No executable code or security risks detected.

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