tessl-labs/health-checks
Health check and readiness endpoints for web services — liveness probes,
97
99%
Does it follow best practices?
Impact
94%
3.61xAverage score across 4 eval scenarios
Passed
No known issues
Evaluation results
100%
72%Build a Todo API with Express
Liveness endpoint exists
0%
100%
Readiness endpoint exists
0%
100%
Readiness returns dependency status
0%
100%
Health endpoints excluded from auth
100%
100%
Dockerfile HEALTHCHECK instruction
0%
100%
Liveness does not check database
0%
100%
503 status for unhealthy readiness
0%
100%
CRUD endpoints functional
100%
100%
Database setup present
100%
100%
92%
72%Build a User Management Service with FastAPI
Liveness endpoint exists
0%
100%
Readiness endpoint exists
0%
100%
Readiness returns structured checks
0%
100%
Graceful startup gating
0%
33%
Liveness does not check database
0%
100%
Dockerfile HEALTHCHECK instruction
0%
100%
503 for unhealthy readiness
0%
100%
CRUD endpoints functional
100%
100%
Unique email constraint
100%
100%
Soft delete implemented
100%
100%
88%
70%Build an Inventory Microservice in Go
Liveness endpoint exists
0%
100%
Readiness endpoint exists
0%
100%
Readiness returns dependency detail
0%
100%
Liveness does not check database
0%
100%
Graceful shutdown
0%
0%
Dockerfile HEALTHCHECK instruction
0%
100%
503 for unhealthy readiness
0%
100%
CRUD endpoints functional
100%
100%
SKU uniqueness enforced
100%
100%
97%
57%Build an Order Processing Service
Liveness endpoint exists
50%
100%
Readiness endpoint checks both dependencies
0%
100%
Readiness returns per-dependency status
0%
100%
Liveness does not check dependencies
0%
100%
Kubernetes liveness probe configured
100%
100%
Kubernetes readiness probe configured
40%
100%
Health endpoints excluded from auth/logging
0%
100%
503 for unhealthy readiness
0%
100%
Order endpoints functional
100%
100%
Kubernetes deployment manifest valid
100%
70%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6