Static analysis reported shell execution, weak cryptography, and reconnaissance patterns. Manual review found a Markdown-only frontend hardening guide with CSS, JSX, JavaScript, and HTML examples, not executable scripts. No prompt injection, data exfiltration, network access, or malicious intent was found.
False Positive: Markdown Backticks Flagged as Shell Execution
The flagged locations are Markdown code fences or inline formatting for CSS, JSX, JavaScript, and HTML examples. I found no Ruby shell backticks, command invocation, or user-controlled shell execution.
The evidence is visible in Markdown examples and prose only. There is no executable Ruby, shell command, subprocess call, or instruction to run external commands.
False Positive: Hardening Language Flagged as Weak Cryptography
The flagged locations discuss interface resilience, long text, ARIA, and global design. I found no MD5, SHA-1, DES, RC4, insecure random generation, or cryptographic implementation.
The surrounding context is user interface guidance, not cryptographic code. No weak algorithm name or cryptographic API appears at the cited lines.
False Positive: UI Layout Guidance Flagged as Reconnaissance
The flagged lines are about flex, grid, typography, and text container sizing. I found no host discovery, OS probing, file enumeration, or system information collection.
The text is plain frontend design guidance. It does not request system commands, environment inspection, or collection of machine details.