Audit-Verlauf

Most flags describe intended proxy operations, Markdown, or protected credential handling; no evidence found of credential harvesting or prompt injection. The opt-in legacy transport branch exposes reusable tokens without encryption. Rotation also invalidates the old token before local storage checks, risking loss of paid access.

Most static matches are Markdown syntax, expected HTTPS requests, local signing, or protected token storage. Confirmed legacy transport paths expose reusable credentials despite explicit opt-in, and malformed credential responses can leak tokens through stdout. No evidence found of prompt injection, unrelated secret harvesting, or intentional malicious exfiltration.

Most detections are Markdown syntax, public service discovery, or expected authentication; no evidence found of prompt injection or unrelated credential exfiltration. Confirmed risks include optional plaintext proxy authentication, unsafe token-file replacement, and recovery signatures in process arguments. Some documented curl examples also print replacement tokens despite nearby secrecy warnings.

Most alerts concern benign documentation or expected credential handling; no evidence of malicious intent or prompt injection was found in the reviewed files. Confirmed risks include plaintext proxy authentication, incomplete payment authorization checks, and exit-identifier injection into curl configuration. Rotation and recovery also discard replacement responses, risking access loss.

All 143 static findings were adjudicated; most describe Markdown, local configuration, or expected service calls, with no evidence found of injection or deliberate exfiltration. Confirmed working proxy examples expose reusable authentication without transport encryption; the authenticated Chromium SOCKS5 example instead fails before connecting. Semantic findings identify token exposure through process arguments and command output, plus absent payment-budget checks in the automatic purchase example.