formatTimeToReset treats 0 as “unknown” due to if (!resetAtOrSeconds). Since reset_after_seconds can be 0 (backend includes the field even when it’s zero), this will incorrectly display “Unknown” instead of an immediate reset/0m. Consider checking resetAtOrSeconds == null (and optionally === '') rather than truthiness so 0 is handled correctly.

formatTimeToReset returns the hardcoded string "Reset now" when the computed reset time is in the past. This bypasses i18n (and differs from other quota labels using t(...)). Please use a translated string/key (or reuse an existing one) for this state.

The check !resetAtOrSeconds will return "Unknown" if the value is 0. However, 0 is a valid value for reset_after_seconds (indicating the quota resets immediately). It is safer to check specifically for null, undefined, or empty strings.

Using toLocaleTimeString here introduces inconsistency with the other date formats in this function (lines 145 and 148), which use a hardcoded 24-hour format (HH:mm). Depending on the user's browser locale, this might show 12-hour time (AM/PM) for today's resets but 24-hour time for others. It is better to use format(date, 'HH:mm') for consistency.

These fields are now displayed unconditionally, which will result in "Unknown" being shown in the UI if the data is missing from the API response. Previously, the resets_at field was conditionally rendered. It is better to wrap these in checks to keep the UI clean when data is unavailable.

            {quotaData.rate_limit?.primary_window?.reset_after_seconds !== undefined && (
              <div className="flex justify-between items-center text-muted-foreground">
                <span>{t('quota.label.reset_in')}</span>
                <span>{formatTimeToReset(quotaData.rate_limit.primary_window.reset_after_seconds)}</span>
              </div>
            )}
            {quotaData.rate_limit?.primary_window?.reset_at && (
              <div className="flex justify-between items-center text-muted-foreground">
                <span>{t('quota.label.resets_at')}</span>
                <span>{formatDate(quotaData.rate_limit.primary_window.reset_at)}</span>
              </div>
            )}

Similar to the primary window, these fields should be conditionally rendered to avoid showing "Unknown" when the specific fields are missing from the secondary window data.

                {quotaData.rate_limit.secondary_window.reset_after_seconds !== undefined && (
                  <div className="flex justify-between items-center text-muted-foreground">
                    <span>{t('quota.label.reset_in')}</span>
                    <span>{formatTimeToReset(quotaData.rate_limit.secondary_window.reset_after_seconds)}</span>
                  </div>
                )}
                {quotaData.rate_limit.secondary_window.reset_at && (
                  <div className="flex justify-between items-center text-muted-foreground">
                    <span>{t('quota.label.resets_at')}</span>
                    <span>{formatDate(quotaData.rate_limit.secondary_window.reset_at)}</span>
                  </div>
                )}

The secondary window block is rendered based on quotaData.rate_limit?.secondary_window?.used_percent !== undefined, but then directly accesses quotaData.rate_limit.secondary_window... within the block. In strict mode, this pattern usually doesn’t narrow rate_limit/secondary_window for TypeScript and can fail type-checking. Suggest storing const secondary = quotaData.rate_limit?.secondary_window; and using secondary after checking it’s defined.

import { Badge ... } is declared mid-file, and the file currently has several imports that are no longer referenced (useMutation, useQueryClient, checkProviderQuotas, toast). With noUnusedLocals: true this will break the TypeScript build. Please move the Badge import up with the other imports and remove any now-unused imports.

formatTimeToReset treats 0 as “missing” because it uses a falsy check (if (!resetAtOrSeconds)). If reset_after_seconds can be 0, the UI will show an empty value instead of something like “0m” / “Reset now”. Use a nullish check (e.g., resetAtOrSeconds == null) so 0 is handled correctly.

In the 5h window block, the condition uses optional chaining (quotaData.windows?.['5h']) but the body accesses quotaData.windows['5h'] directly. In strict mode this typically won’t narrow windows/['5h'] for TypeScript, and can lead to type errors. Consider assigning const w5h = quotaData.windows?.['5h']; and using w5h inside the block.

In the primary window section, the guard is quotaData.rate_limit?.primary_window && (...) but inside the block the code accesses quotaData.rate_limit.primary_window... without optional chaining. With strict: true, optional chaining in the condition generally doesn’t narrow rate_limit for the body, so this can cause TS errors. Prefer capturing const primary = quotaData.rate_limit?.primary_window; and using primary throughout the block.