Generate tamper-evident, fingerprinted Kubernetes verification receipts as in-toto Statements.
npx skills add https://github.com/confighub/cub-scout --skill scout-verify
Please help me install this Agent Skill. Skill: scout-verify Source: https://github.com/confighub/cub-scout/tree/main/skills/scout-verify Command: npx skills add https://github.com/confighub/cub-scout --skill scout-verify
It turns Kubernetes verification results into an immutable, fingerprinted evidence artifact you can store, share, and re-validate for audit trails, CI gates, and postmortems.
Run scout-verify to verify a Kubernetes resource and save an immutable receipt for your audit trail and CI gate.
High-intent search queries and answers about installing and using this skill.
To create tamper-evident Kubernetes audit receipts for CI gating, generate fingerprinted in-toto Statement v1 artifacts containing verdicts and evidence. These immutable receipts persist cluster state compliance records for storage, re-validation, and release promotion gates.
A tamper-evident receipt for Kubernetes cluster state compliance is a typed, fingerprinted artifact that proves verification results were not edited after creation. It records source-truth alignment and applied-matches-spec verdicts for audit trails and postmortems.
You can validate that no manual edits occurred in Kubernetes resources during a freeze window by generating a receipt with the no-manual-edits-since predicate. This attestation fingerprint confirms resource state alignment against source-truth at a specific point in time.
Store immutable evidence artifacts for Kubernetes postmortems by exporting tamper-evident receipts as in-toto Statement v1 documents. Recompute the receipt fingerprint later to validate the artifact was not tampered with since it was originally stamped.
Generating Kubernetes verification receipts does not require write access to the cluster. The receipt generation process supports strict read-only access to evaluate cluster state compliance and produce typed attestations without modifying resources.
The best way to maintain a GitOps audit trail for Kubernetes compliance is to produce persisted, typed attestations that record source-truth-pass and applied-matches-spec verdicts. These fingerprinted receipts provide stable historical records rather than relying on ephemeral comparisons.
confighubCompare intended Kubernetes state against live cluster state for drift.
confighubGenerate incident close-out evidence packs with fingerprinted receipts and chained attestations.
kcns008Automate GitOps deployments and CI/CD pipelines for Kubernetes and OpenShift clusters.
confighubGenerate quarterly Kubernetes compliance reports with per-resource violations and fingerprinted evidence.
