prod-readiness

Auditing a codebase for production readiness involves scanning deployment configurations and source code to identify operational, reliability, observability, and security gaps. This process applies 24 independent checks to APIs and containerized applications to ensure safe release operations.

A production readiness review evaluates health checks, shutdown behavior, retries, timeouts, logging, metrics, security controls, resource limits, migrations, rate limiting, and documentation. It identifies deployment gaps that prevent a codebase from being safe and reliable in production environments.

Yes, production readiness audits apply to TypeScript APIs, services, containerized applications, and CI/CD configurations. The audit detects stack-specific issues like missing health probes, weak dependency handling, and absent vulnerability scanning before deployment.

Generating an evidence-backed scorecard requires running independent parallel judges and three-search verification against the codebase. It produces categorized PASS, WARN, FAIL, and N/A statuses with severity ratings and exact file-and-line evidence to reduce unsupported conclusions.

The best way to find missing observability and security controls is performing a 24-point codebase audit using verbatim file-line evidence. This structured review identifies absent vulnerability scanning, incomplete operational configuration, and missing metrics before release.

Automated production readiness audits are not suited for post-incident debugging or runtime monitoring. They are designed for pre-deployment or pre-release infrastructure reviews and codebase evaluation, not for actively resolving ongoing production incidents.