feat: Add support for scanning specific rules - #733

Kusari Analysis Results:

✅ No Flagged Issues Detected
All values appear to be within acceptable risk parameters.

Both dependency and code analyses recommend proceeding. No dependency changes were detected, eliminating supply chain risk. The sole code finding is a medium-impact, low-likelihood XSS issue in pkg/server/server.go (lines 142 and 150), where error messages derived from the 'rule' query parameter are written to the HTTP ResponseWriter without HTML escaping. Since kubesec is a security analysis API tool rather than a browser-facing HTML application, the practical XSS risk is minimal. No critical or high-severity issues, secrets, or workflow vulnerabilities were identified. Before merging, it is recommended to add a Content-Type header set to 'text/plain; charset=utf-8' before writing error responses, which eliminates the XSS surface entirely: w.Header().Set("Content-Type", "text/plain; charset=utf-8") followed by w.WriteHeader(http.StatusBadRequest) and the existing fmt.Fprintf call. This is a low-effort hardening step that reduces theoretical browser-based misinterpretation of error payloads.

@kusari-inspector rerun - Trigger a re-analysis of this PR
@kusari-inspector feedback [your message] - Send feedback to our AI and team
See Kusari's documentation for setup and configuration.
Commit: 5f37ab2, performed at: 2026-06-09T10:56:08Z