caching-audit

To audit Redis caching across API endpoints, run this tool to scan all public routes, detect missing caches for expensive calls, flag unbounded TTLs, and identify missing timeout guards, producing a structured report with actionable recommendations.

An unbounded TTL is a cache expiration set without a time limit, which can cause stale data and memory bloat. This audit identifies unbounded TTLs on Redis caches and validates TTL alignment with actual data volatility to prevent performance degradation.

You can check for missing Redis cache coverage by applying this audit to all public API routes, which automatically excludes internal endpoints and surfaces expensive calls that lack caching, then details the findings in a comprehensive report.

Yes, you can review Vite chunk configuration during a Redis cache audit. This tool includes a specific check for Vite chunk configuration to ensure proper code-splitting and verify that your frontend builds remain cache-friendly.

No, the caching audit does not modify your source code. It performs a read-only review of your Redis operations, TTL configurations, and timeout guards, delivering a structured report of findings and recommendations for engineering teams to implement manually.

The best way to identify weak timeout guards is to run an audit that inspects Redis operations and rate-limiter usage across all API routes. This tool flags missing or weak timeout configurations and includes them in a structured performance report.