All 33 static detections are false positives caused by Markdown formatting, local example URLs, safe device output, or ordinary technical prose. One semantic issue remains: the FastAPI example exposes raw exception details in client responses.
All 33 static alerts are false positives caused by Markdown formatting, local examples, or ordinary backend terminology. Two medium semantic issues remain in the sample guidance: exception details may reach clients, and cryptographic advice is ambiguous. No prompt injection or malicious intent was found.
The guidance presents AES-256 and bcrypt as encryption alternatives, although bcrypt is irreversible and AES security depends on mode and key handling.
Line 56 explicitly groups AES-256 and bcrypt under sensitive-field encryption. The recommendation can lead to incorrect protection choices.
All 33 static alerts are false positives caused by Markdown formatting, local examples, or ordinary backend terminology. Two medium semantic issues remain in the sample guidance: exception details may reach clients, and cryptographic advice is ambiguous. No prompt injection or malicious intent was found.
The guidance presents AES-256 and bcrypt as encryption alternatives, although bcrypt is irreversible and AES security depends on mode and key handling.
Line 56 explicitly groups AES-256 and bcrypt under sensitive-field encryption. The recommendation can lead to incorrect protection choices.
All 33 static alerts are false positives caused by Markdown formatting, local examples, or ordinary backend terminology. Two medium semantic issues remain in the sample guidance: exception details may reach clients, and cryptographic advice is ambiguous. No prompt injection or malicious intent was found.
The guidance presents AES-256 and bcrypt as encryption alternatives, although bcrypt is irreversible and AES security depends on mode and key handling.
Line 56 explicitly groups AES-256 and bcrypt under sensitive-field encryption. The recommendation can lead to incorrect protection choices.