Complete helm toolkit with generation and validation capabilities
94
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
{
"context": "Tests whether the agent avoids hardcoding image tags, always sets resource limits and requests, and correctly structures values.yaml with sensible defaults and documentation comments.",
"type": "weighted_checklist",
"checklist": [
{
"name": "No hardcoded image tag",
"description": "The image tag in values.yaml is set to an empty string or a variable reference (e.g., tag: \"\"), NOT a literal version string like 'v2.1.0' or 'latest'",
"max_score": 14
},
{
"name": "appVersion default",
"description": "Chart.yaml includes an appVersion field, and/or the deployment template falls back to .Chart.AppVersion when the tag value is empty",
"max_score": 10
},
{
"name": "Resources block present",
"description": "The deployment template or values.yaml contains a resources: block with at least one CPU or memory entry under both requests and limits",
"max_score": 14
},
{
"name": "Both requests and limits",
"description": "The resources block specifies values under BOTH requests: and limits: (not just one of them)",
"max_score": 10
},
{
"name": "values.yaml comments",
"description": "values.yaml contains inline documentation comments (lines starting with #) describing the purpose of at least 3 distinct settings",
"max_score": 8
},
{
"name": "Liveness probe defined",
"description": "The deployment template includes a livenessProbe block pointing to a path or exec command",
"max_score": 8
},
{
"name": "Readiness probe defined",
"description": "The deployment template includes a readinessProbe block pointing to a path or exec command",
"max_score": 8
},
{
"name": "Security context present",
"description": "Either values.yaml or the deployment template includes a securityContext section (pod-level or container-level)",
"max_score": 8
},
{
"name": "Image repository separate",
"description": "In values.yaml the image is split into at least repository: and tag: sub-keys, rather than a single combined image: string",
"max_score": 10
},
{
"name": "Related settings grouped",
"description": "values.yaml groups related settings under named keys (e.g., image:, resources:, probes: or similar) rather than a flat list of top-level keys",
"max_score": 10
}
]
}