Audit History
flutter-animations - 4 audits
Version comparison
Capability and finding changes across audited versions, newest first.
| Version | Date | Result | Review items | Change vs previous |
|---|---|---|---|---|
| v4 Latest | Jul 6, 2026, 07:00 PM | No confirmed findings | 0 | No capability change |
| v3 | Jul 6, 2026, 07:00 PM | No confirmed findings | 0 | External commands |
| v2 | Jun 30, 2026, 07:27 AM | No confirmed findings | 0 | External commands |
| v1 | Feb 13, 2026, 08:54 AM | No confirmed findings | 0 | Baseline |
Jul 6, 2026, 07:00 PM
All static findings were adjudicated as false positives. The sensitive detections are Flutter super.key syntax, the blocker detections are Dart lifecycle or documentation text, and the external command detections are Markdown backticks around Dart examples. No prompt injection, credential exposure, command execution, or exfiltration intent was found.
Risk Factors
⚙️ External commands (82)
Jul 6, 2026, 07:00 PM
All static findings were adjudicated as false positives. The sensitive detections are Flutter super.key syntax, the blocker detections are Dart lifecycle or documentation text, and the external command detections are Markdown backticks around Dart examples. No prompt injection, credential exposure, command execution, or exfiltration intent was found.
Risk Factors
⚙️ External commands (82)
Jun 30, 2026, 07:27 AM
AI review found the static findings to be false positives from Flutter and Markdown syntax, including super.key, @override, code fences, and animation physics terminology. No shell execution, network access, filesystem access, credential handling, data exfiltration, or prompt-injection attempt was found in the reviewed files.
Static false positives ignored (4)
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.
Feb 13, 2026, 08:54 AM
This is a documentation/reference skill for Flutter animations. Static scanner flagged Flutter Curve class methods (Curves.easeIn, Curves.bounceIn) as 'certificate/key files' and 'weak cryptographic algorithms' - these are false positives. The backtick detections are markdown code blocks in documentation files. No real security concerns found. Safe for publication.