AI Fix Prompts for Gold Dashboard Arena

Fix a hardcoded credential in repository 'tah-allotrope__gold-dashboard-arena'.

**Issue**: Hard-coded sast found ([sast:aljefra/ssrf-http-client] SSRF via HTTP Client with Dynamic URL)
**File**: public/app.js
**Line**: 431
**Severity**: HIGH

**Current code around the issue:**
```
     426 | 
     427 | let lastData = null;
     428 | 
     429 | async function fetchData() {
     430 |     try {
>>>  431 |         const response = await fetch(`${DATA_URL}?t=${Date.now()}`);
     432 |         if (!response.ok) throw new Error(`HTTP ${response.status}`);
     433 |         const data = await response.json();
     434 |         lastData = data;
     435 | 
     436 |         const goldHistory = data.history && data.history.gold;
```

**Required fix:**
1. Remove the hardcoded credential from the source code
2. Replace it with an environment variable read: `os.environ.get('SAST_KEY')` (Python) or `process.env.SAST_KEY` (JS)
3. Add the variable name to a `.env.example` file with a placeholder value
4. Ensure `.env` is in `.gitignore`
5. If this credential was ever committed to git, it should be considered compromised and rotated

**Do NOT:**
- Move the secret to a config file that gets committed
- Use a default fallback value that is a real credential
- Leave the old credential in a comment

Fix a hardcoded credential in repository 'tah-allotrope__gold-dashboard-arena'.

**Issue**: Hard-coded sast found ([sast:aljefra/ssrf-requests] SSRF via HTTP Client with Variable URL)
**File**: scripts/debug_alternative_gold.py
**Line**: 26
**Severity**: HIGH

**Current code around the issue:**
```
      21 |     print(f"Testing: {name}")
      22 |     print(f"URL: {url}")
      23 |     print('='*60)
      24 |     
      25 |     try:
>>>   26 |         response = requests.get(url, headers=HEADERS, timeout=REQUEST_TIMEOUT, verify=False)
      27 |         response.raise_for_status()
      28 |         
      29 |         print(f"Status: {response.status_code}")
      30 |         print(f"Content-Type: {response.headers.get('Content-Type', 'unknown')}")
      31 |         print(f"Content length: {len(response.content)} bytes")
```

**Required fix:**
1. Remove the hardcoded credential from the source code
2. Replace it with an environment variable read: `os.environ.get('SAST_KEY')` (Python) or `process.env.SAST_KEY` (JS)
3. Add the variable name to a `.env.example` file with a placeholder value
4. Ensure `.env` is in `.gitignore`
5. If this credential was ever committed to git, it should be considered compromised and rotated

**Do NOT:**
- Move the secret to a config file that gets committed
- Use a default fallback value that is a real credential
- Leave the old credential in a comment

Address OWASP A02 (Cryptographic Failures) compliance gap in 'tah-allotrope__gold-dashboard-arena'.

**OWASP Category**: A02 -- Cryptographic Failures
**Fix guidance**: Remove hardcoded secrets, use strong encryption (AES-256-GCM), enforce TLS, never store passwords in plaintext (use bcrypt/argon2).

**Steps:**
1. Identify all code paths related to cryptographic failures
2. Apply the fixes described above
3. Add automated tests to verify the fix
4. Document any security assumptions in code comments

Address OWASP A06 (Vulnerable Components) compliance gap in 'tah-allotrope__gold-dashboard-arena'.

**OWASP Category**: A06 -- Vulnerable Components
**Fix guidance**: Update all dependencies to latest stable versions, remove unused dependencies, monitor for new CVEs.

**Steps:**
1. Identify all code paths related to vulnerable components
2. Apply the fixes described above
3. Add automated tests to verify the fix
4. Document any security assumptions in code comments

Repository 'tah-allotrope__gold-dashboard-arena' is failing the quality gate.

Failed conditions:
- overall_score: actual 0.0 >= 50 (FAILED)
- security_score: actual 0.0 >= 40 (FAILED)

Fix each failing condition to make the repo pass the quality gate.

Repository 'tah-allotrope__gold-dashboard-arena' has 6 open issues:

- [HIGH] Hard-coded sast: [sast:aljefra/ssrf-http-client] SSRF via HTTP Client with Dynamic URL (public/app.js)
- [HIGH] Hard-coded sast: [sast:aljefra/ssrf-requests] SSRF via HTTP Client with Variable URL (scripts/debug_alternative_gold.py)
- [MEDIUM] GHSA-w8v5-vhqr-4h9v: diskcache
- [MEDIUM] GHSA-9hjg-9r4m-mvj7: requests
- [MEDIUM] GHSA-9wx4-h78v-vm56: requests
- [MEDIUM] GHSA-gc5v-m9x4-r6x2: requests

Resolve each issue. For security issues, apply the appropriate fix. For quality issues, refactor the affected code.

Static analysis found 2 security issues in 'tah-allotrope__gold-dashboard-arena':

- [HIGH] [sast:aljefra/ssrf-http-client] SSRF via HTTP Client with Dynamic URL at public/app.js:431
- [HIGH] [sast:aljefra/ssrf-requests] SSRF via HTTP Client with Variable URL at scripts/debug_alternative_gold.py:26

For each finding:
- SQL injection: use parameterized queries
- Command injection: use subprocess with list args, no shell=True
- Path traversal: validate and sanitize paths
- Insecure deserialization: use json instead of pickle
- IaC misconfigs: apply the suggested fix from the rule