tessl-labs/configuration-management
Production config management for any backend — centralized config module, env vars, no hardcoded secrets, fail-fast validation
86
77%
Does it follow best practices?
Impact
100%
1.88xAverage score across 5 eval scenarios
Passed
No known issues
Evaluation results
100%
43%Build a Blog CMS API
Centralized config module
0%
100%
Database URL from environment
85%
100%
AWS credentials from environment
85%
100%
Required config fails fast
14%
100%
No hardcoded secrets
100%
100%
Env file gitignored
100%
100%
.env.example exists
0%
100%
Post endpoints functional
100%
100%
100%
54%Build an Email Notification Service
Centralized config module
0%
100%
SendGrid API key from environment
75%
100%
Required config fails fast
0%
100%
No hardcoded secrets
100%
100%
Env file gitignored
100%
100%
.env.example exists
0%
100%
Database path configurable
0%
100%
Notification endpoints functional
100%
100%
100%
44%Build a Payment Processing API
Centralized config module
0%
100%
Database URL from environment
100%
100%
Stripe keys from environment
100%
100%
Required config fails fast
0%
100%
Env file gitignored
100%
100%
.env.example exists
0%
100%
Port from environment with default
100%
100%
Payment endpoints functional
100%
100%
100%
58%Build a User Authentication Service
Centralized config module
0%
100%
Database URL from environment
71%
100%
JWT secret from environment
62%
100%
Required config fails fast
0%
100%
No hardcoded secrets
33%
100%
Env file gitignored
100%
100%
.env.example exists
0%
100%
Auth endpoints functional
100%
100%
100%
34%Build a Weather Dashboard Backend
Centralized config module
33%
100%
OpenWeatherMap API key from environment
100%
100%
Required config fails fast
0%
100%
Redis URL from environment
100%
100%
No hardcoded secrets
100%
100%
Env file gitignored
100%
100%
.env.example exists
0%
100%
Weather endpoints functional
100%
100%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6