How to inspect Kubernetes YAML without uploading it
A Kubernetes manifest is a security decision written in YAML. The dangerous settings — privileged: true, a container running as root, a hostPath mount on the Docker socket — are one line each, and they are exactly the lines that get copied from a tutorial and never revisited. Catching them after the apply means an incident; catching them before costs a paste.
This tool checks the manifest where it already is: on your own device. When you paste a manifest or drop a YAML file here, your browser:
- Parses every document — multi-document files separated by --- are split and checked one by one, with a small built-in YAML parser that covers the block mappings, sequences, quoted and plain scalars, flow collections and block scalars that real manifests use.
- Runs the risk checks per container — privileged mode, root user, host namespaces, missing limits and requests, :latest images, missing liveness and readiness probes, dangerous capabilities, secrets in plain environment variables, hostPath mounts, seccomp and read-only root filesystem settings — plus pod-level, Service, Secret, Ingress and RBAC checks.
- Scores and explains — every finding carries a severity, a plain-English explanation of why it matters, and a suggested fix with a line number, and the whole inspection rolls up into a risk score out of 100 and a downloadable report.
What makes this inspector different
The established scanners in this space are command-line tools — Kubesec, KubeLinter, kube-score — which you install and run in a terminal or CI. The hosted services that accept a paste either send your manifest to their server or check only syntax and schema. The browser tools that do exist check a narrower rule set: missing limits, missing probes and :latest tags, without the securityContext checks, the secrets-in-env check, the host-namespace checks or a downloadable report. This page is the only free, fully client-side inspector we found that combines the full security and reliability rule set with a risk score, per-finding fixes and a downloadable report — with no install, no account, no upload, and a live network-request counter so you can verify the privacy claim yourself.
When is inspecting the right choice — and when is it the wrong one?
Inspecting is right before a first apply, before a pull request merges a manifest change, and when you inherit a cluster's manifests and want to know what you are running. It is the wrong choice as a substitute for a cluster audit: this tool cannot see your image vulnerabilities, your RBAC bindings, or what is actually running — only what the manifest says. It is also the wrong choice as an admission policy: it reports, it does not block. For that, enforce the same rules with an admission controller.
Honest limitations
Heuristic checks, not an audit
These are widely known hardening rules applied to a static file. They cannot replace kube-bench, kubeaudit, KubeLinter, or an admission policy — and a clean score means none of these checks fired, not that the manifest is secure.
It never sees your cluster
The tool cannot check image vulnerabilities, RBAC bindings, NetworkPolicies, or what is actually running. A manifest can pass every check here and still deploy a vulnerable image.
Templates are not evaluated
Helm and Go template expressions are treated as unknown values, never guessed. Render the manifest first (helm template, for example) and paste the rendered output for a full inspection.
Anchors and aliases are not resolved
The built-in parser covers common manifests. Complex anchors, merge keys and unusual flow styles may not parse — the inspection reports what it could not parse rather than guessing.
Severity weights are judgement
Critical deducts 20, high 12, medium 6 and low 3. Those numbers are this tool's judgement, documented openly — a team with different risk tolerance may reasonably score the same manifest differently.
It never changes your files
This tool only reports and downloads a new report. Your manifest files are never modified — to fix a risk, edit the manifest yourself and re-inspect.