fix(usage): use secure random longitude

[kilo-code-bot]

Summary

• Replace the longitude benchmark fixture's Math.random() call with Node crypto-backed randomInt() to resolve CodeQL alert 247 without changing the generated coordinate range.
• Keep the fix scoped to the reported apps/web/src/scripts/usage/benchmark-insert-usage.ts finding.

Verification

• Not run manually; this is a non-UI benchmark data-generation script change with no manual user flow.

Visual Changes

N/A

Reviewer Notes

• Targeted at https://github.com/Kilo-Org/cloud/security/code-scanning/247.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Executive Summary

The longitude fix is correct and resolves the CodeQL alert, but the identical Math.random() pattern for latitude (line 141) is left unfixed and would trigger the same class of alert.

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
apps/web/src/scripts/usage/benchmark-insert-usage.ts	141	Latitude still uses Math.random() — identical pattern to the fixed longitude

Other Observations (not in diff)

Issues found in unchanged code that cannot receive inline comments:

apps/web/src/scripts/usage/benchmark-insert-usage.ts, line 141

The longitude was replaced with secureRandomInt to resolve CodeQL alert 247, but the latitude uses the identical Math.random() * 180 - 90 pattern. If the CodeQL rule is flagging Math.random() for geographic coordinate generation, this line would trigger the same class of finding. Consider applying the same fix:

http_x_vercel_ip_latitude: maybeNull(
  secureRandomInt(0, 180_000_000) / 1_000_000 - 90,
  metaStats.vercel_ip_latitude_null_pct
),

Note: since this is a benchmark data-generation script (not security-sensitive production code), the risk is low, but fixing both together would make the codebase consistent and prevent a follow-up CodeQL alert.

Files Reviewed (1 file)

• apps/web/src/scripts/usage/benchmark-insert-usage.ts — 1 issue

Fix these issues in Kilo Cloud

---

_{Reviewed by claude-4.6-sonnet-20260217 · 308,815 tokens}

_{Review guidance: REVIEW.md from base branch main}