📦

Audit History

quality-manager-qmr - 6 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v6 LatestJul 6, 2026, 01:53 AM No confirmed findings0No capability change
v5 Jul 6, 2026, 01:53 AM No confirmed findings0Env variablesExternal commands
v4 Jun 28, 2026, 09:29 AM No confirmed findings0 External commandsEnv variables
v3 Jan 16, 2026, 04:34 PM No confirmed findings0No capability change
v2 Jan 16, 2026, 04:34 PM No confirmed findings0No capability change
v1 Jan 15, 2026, 11:40 AM No confirmed findings0Baseline

Jul 6, 2026, 01:53 AM

All static findings were assessed as false positives after reviewing the referenced skill text and evaluation content. The flagged external command items are markdown fences or inline file and directory names, while environment and reconnaissance items are ordinary QMR governance prose with no executable behavior.

5
Files scanned
601
Lines analyzed
2
Review items
0
False positives ignored
Audited by: codex

Jul 6, 2026, 01:53 AM

All static findings were assessed as false positives after reviewing the referenced skill text and evaluation content. The flagged external command items are markdown fences or inline file and directory names, while environment and reconnaissance items are ordinary QMR governance prose with no executable behavior.

5
Files scanned
601
Lines analyzed
2
Review items
0
False positives ignored
Audited by: codex

Jun 28, 2026, 09:29 AM

The static analyzer reported many high-risk patterns, but the cited lines are documentation, markdown formatting, or prior evaluation text. I found no evidence of prompt injection, credential access, network calls, weak cryptography, or command execution intent in the reviewed files.

5
Files scanned
601
Lines analyzed
0
Review items
3
False positives ignored
Static false positives ignored (3)

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
Weak Cryptography Detections Are False Positives
Static weak-cryptography alerts point to QMR, R&D, placeholder asset text, and evaluation content. No evidence found for cryptographic APIs, weak hashing, encryption, or password handling.
The reviewed locations contain regulatory and documentation terms, not cryptographic code. The package has no observed crypto operations in the cited files.
Low
Markdown Backtick Detections Are False Positives
The external-command alerts point to markdown fences and inline filenames. No evidence found for shell execution, Ruby backticks, dynamic command construction, or command invocation.
The cited lines are markdown code fences or resource-name formatting. They do not include executable commands or user-controlled inputs.
Low
Environment And Network Detections Are False Positives
The configuration and network reconnaissance alerts point to management review text, regulatory communication wording, and prior evaluation examples. No evidence found for environment variable reads or network scanning behavior.
The line context is quality management and regulatory documentation. There are no environment APIs, host probes, scanners, or outbound network instructions at these locations.
No confirmed security findings were recorded for this completed audit.
Audited by: codex

Jan 16, 2026, 04:34 PM

This is a documentation-only skill containing markdown files with quality management frameworks. No executable code, scripts, network operations, or cryptographic operations exist. All 63 static findings are false positives caused by the scanner misidentifying ASCII tree diagram characters as shell backticks, file format names as cryptographic patterns, and regulatory compliance text as security threats.

6
Files scanned
917
Lines analyzed
2
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (2)
🔑 Env variables (1)
Audited by: claude

Jan 16, 2026, 04:34 PM

This is a documentation-only skill containing markdown files with quality management frameworks. No executable code, scripts, network operations, or cryptographic operations exist. All 63 static findings are false positives caused by the scanner misidentifying ASCII tree diagram characters as shell backticks, file format names as cryptographic patterns, and regulatory compliance text as security threats.

6
Files scanned
917
Lines analyzed
2
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (2)
🔑 Env variables (1)
Audited by: claude

Jan 15, 2026, 11:40 AM

Documentation-only skill with no executable code. All 24 static findings are false positives: ASCII art tree diagrams (Unicode box characters) misinterpreted as shell backticks, file format names misinterpreted as cryptographic algorithms, and regulatory compliance text misinterpreted as network reconnaissance.

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