Kubernetes Manifest Studio
Generate Deployment, Service, and Ingress YAML with a drift checklist.
OpenA quick pattern check for obvious credentials before text leaves your hands.
Add code, config, a log or a diff.
Five credential patterns are checked as you type.
Each finding shows its type and the start of the match.
Revoke real keys, then remove them from the text.
You are about to paste a failing CI log into a public issue, and it includes a dump of environment variables. One scan for anything that looks like a key is far cheaper than rotating credentials afterwards.
The scanner looks for five patterns: AWS access key IDs starting with AKIA, GitHub personal access tokens starting with ghp_, keys in the sk- style used by OpenAI and some other APIs, PEM headers for RSA, OpenSSH or generic private keys, and any password = assignment with a value after it. Each hit is listed with its type and the first 24 characters of the match, up to 40 hits. A clean result reads No obvious secrets found.
The word obvious matters. The patterns are narrow, so password: in YAML, fine-grained or OAuth GitHub tokens, Slack and Stripe keys, JWTs and database URLs with embedded passwords are not detected. For .env files, the dotenv linter checks a longer list of credential formats. The preview is not a redaction either: an AWS key ID is only 20 characters, so it appears in full. If a real key turns up, rotate it rather than just deleting the line.
Scanning happens in your browser, which is the point, since the text you are worried about stays put. For Dockerfiles with credentials in ENV or ARG, the Dockerfile review tool flags them with line numbers, and the binary path checker covers the other common repo hygiene problem.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
Stripe keys use an underscore, as in sk_live_, while this scanner looks for sk- with a hyphen. The Env Validator in the same category includes a Stripe live key pattern.
Only partly. It shows up to 24 characters of each match, which is enough to reveal a whole AWS access key ID. Do not paste the findings anywhere public either.