Audit History
incident-response-incident-response - 5 audits
Version comparison
Capability and finding changes across audited versions, newest first.
| Version | Date | Result | Review items | Change vs previous |
|---|---|---|---|---|
| v5 Latest | Jul 24, 2026, 01:06 AM | No confirmed findings | 0 | No capability change |
| v4 | Jul 8, 2026, 02:19 PM | No confirmed findings | 0 | No capability change |
| v3 | Jul 7, 2026, 01:12 AM | 1 confirmed | 0 | No capability change |
| v2 | Jun 30, 2026, 04:10 PM | 1 confirmed | 0 | External commands |
| v1 | Feb 25, 2026, 04:57 AM | No confirmed findings | 0 | Baseline |
Jul 24, 2026, 01:06 AM
All seven static findings are false positives. The backticks delimit a Markdown path, while the other matches are ordinary incident-response prose and telemetry guidance. No prompt injection, exfiltration intent, executable code, or unauthorized reconnaissance was found.
Risk Factors
⚙️ External commands (1)
Jul 8, 2026, 02:19 PM
The static external command finding is a Markdown formatting false positive. The reconnaissance findings describe authorized SRE incident response activities, and no prompt injection or exfiltration intent was found in SKILL.md.
Risk Factors
⚙️ External commands (1)
Jul 7, 2026, 01:12 AM
The static command and reconnaissance matches are mostly false positives caused by markdown references and incident-response terminology. I found a separate medium-risk operational safety issue: the skill asks agents to implement mitigations and emergency deployments without explicit approval gates.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (1)
Jun 30, 2026, 04:10 PM
Static analysis reported shell execution, weak cryptography, system reconnaissance, and network reconnaissance patterns. Review found these are false positives caused by Markdown backticks and incident response terminology, with no executable code, no cryptographic implementation, and no hostile reconnaissance instructions. The skill does ask agents to coordinate high-impact operational tasks, so users should apply normal change-control safeguards.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (1)
Feb 25, 2026, 04:57 AM
All 11 static findings are false positives. The skill is a legitimate incident response workflow guide (markdown documentation). The 'external_commands' detection refers to markdown backticks for file paths, not shell execution. The 'weak cryptographic algorithm' and 'system/network reconnaissance' detections are scanner misinterpretations of incident response terminology (severity levels, observability analysis, root cause analysis). No actual security risks present.
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.