Audit History
auth-implementation-patterns - 8 audits
Version comparison
Capability and finding changes across audited versions, newest first.
| Version | Date | Result | Review items | Change vs previous |
|---|---|---|---|---|
| v8 Latest | Jul 7, 2026, 07:47 AM | 1 confirmed | 0 | No capability change |
| v7 | Jul 7, 2026, 07:47 AM | 1 confirmed | 0 | External commands |
| v6 | Jun 30, 2026, 09:58 PM | No confirmed findings | 2 | No capability change |
| v5 | Jun 30, 2026, 09:58 PM | No confirmed findings | 2 | External commands |
| v4 | Jan 17, 2026, 07:22 AM | No confirmed findings | 0 | No capability change |
| v3 | Jan 17, 2026, 07:22 AM | No confirmed findings | 0 | External commandsEnv variables |
| v2 | Jan 4, 2026, 04:47 PM | No confirmed findings | 0 | No capability change |
| v1 | Jan 4, 2026, 04:47 PM | No confirmed findings | 0 | Baseline |
Jul 7, 2026, 07:47 AM
The static shell, environment, sensitive file, and reconnaissance findings are false positives caused by Markdown fences and non-executed TypeScript examples. No prompt injection or malicious exfiltration intent was found. One content-level issue remains: the OAuth example places an access token in a URL query string.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (18)
🔑 Env variables (23)
Jul 7, 2026, 07:47 AM
The static shell, environment, sensitive file, and reconnaissance findings are false positives caused by Markdown fences and non-executed TypeScript examples. No prompt injection or malicious exfiltration intent was found. One content-level issue remains: the OAuth example places an access token in a URL query string.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (18)
🔑 Env variables (23)
Jun 30, 2026, 09:58 PM
The static shell-execution, browser credential, browser storage, weak cryptography, and reconnaissance findings are false positives caused by Markdown code fences, auth terminology, and best-practice text. The skill contains no executable script files, but one OAuth example redirects an access token in a URL query string, which is unsafe implementation guidance. Publication is acceptable with a warning or content correction.
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Static false positives ignored (1)
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.
Risk Factors
Detected Patterns
Jun 30, 2026, 09:58 PM
The static shell-execution, browser credential, browser storage, weak cryptography, and reconnaissance findings are false positives caused by Markdown code fences, auth terminology, and best-practice text. The skill contains no executable script files, but one OAuth example redirects an access token in a URL query string, which is unsafe implementation guidance. Publication is acceptable with a warning or content correction.
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Static false positives ignored (1)
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.
Risk Factors
Detected Patterns
Jan 17, 2026, 07:22 AM
Pure documentation skill containing authentication code examples. All code is illustrative TypeScript demonstrating secure patterns (bcrypt with 12 rounds, JWT, proper cookie flags). No executable code, shell commands, network calls, or file system access beyond reading its own files. Static findings are false positives triggered by markdown code block backticks, environment variable references in examples, and security library mentions. The previous audit correctly identified this as safe.
Risk Factors
⚙️ External commands (18)
🔑 Env variables (23)
Jan 17, 2026, 07:22 AM
Pure documentation skill containing authentication code examples. All code is illustrative TypeScript demonstrating secure patterns (bcrypt with 12 rounds, JWT, proper cookie flags). No executable code, shell commands, network calls, or file system access beyond reading its own files. Static findings are false positives triggered by markdown code block backticks, environment variable references in examples, and security library mentions. The previous audit correctly identified this as safe.
Risk Factors
⚙️ External commands (18)
🔑 Env variables (23)
Jan 4, 2026, 04:47 PM
Pure documentation skill containing only code examples and patterns. No executable scripts, network calls, file system access beyond its own files, or external commands. All code snippets are illustrative and demonstrate authentication patterns without any malicious capabilities.
Jan 4, 2026, 04:47 PM
Pure documentation skill containing only code examples and patterns. No executable scripts, network calls, file system access beyond its own files, or external commands. All code snippets are illustrative and demonstrate authentication patterns without any malicious capabilities.