No user-submitted related servers found.
Scored across 5 tools
kubeguard_scan (inline manifest text) and kubeguard_scan_path (directory of YAML files) share the auditing purpose but have clearly different inputs, and the descriptions make that distinction explicit. kubeguard_demo also produces an audit but is framed as sample generation, so it is unlikely to be misselected. Only the scan/scan_path pair presents mild ambiguity.
All tools use a uniform kubeguard_ snake_case prefix, which makes the family immediately recognizable. The suffix style mixes verbs (scan, scan_path, demo) with nouns (rules, rbac), a minor deviation from a pure verb_noun pattern but still readable and predictable.
Five tools is well-scoped for a focused Kubernetes manifest auditor, and each tool covers a distinct capability: text scan, directory scan, rule catalog, RBAC analysis, and demo. There is no redundant or filler tool.
The set covers the core audit lifecycle: discovering rules, scanning inputs in two forms, analyzing RBAC, and a demo entry point for onboarding. Gaps are minor for a read-only auditor, but there is no way to apply or export fixes, suppress/config rules, or scan a live cluster, so agents must handle remediation outside the server.