⚠️ Security: Potential AWS Secret Access Key (potential) Leak Detected

## ⚠️ Potential API Key Leak Detected

**Automated Security Notice**

Hi! 👋

An automated security scan detected a potential API key in your repository:

| Detail | Value |
|--------|-------|
| **File** | `llms.txt` |
| **Key Type** | AWS Secret Access Key (potential) |
| **Severity** | HIGH |
| **Detected** | 2026-04-08T07:01:05.598824+00:00 |

### 🚨 What You Should Do

1. **Rotate the key immediately** (revoke and generate new one)
2. **Remove this file from git history** (use `git filter-branch` or BFG Repo-Cleaner)
3. **Use environment variables** instead of hardcoding credentials
4. **Add sensitive files to `.gitignore`** to prevent future leaks

### 📚 Resources

- [GitHub Secret Scanning](https://docs.github.com/en/code-security/secret-scanning)
- [12 Factor App - Config](https://12factor.net/config)
- [GitGuardian - Secrets in Git](https://blog.gitguardian.com/secrets-api-management/)
- [AWS Secret Access Key (potential) Security Docs](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html)

### 🔧 Coming Soon

A future update will include automated pull requests with suggested fixes:
- Remove leaked credentials
- Add `.gitignore` entries
- Create `.env.example` templates

For now, please review the file manually and secure your credentials!

### 🤖 About This Alert

This is an automated security notice from Raccoon Key Scanner.
We scan public repos for leaked credentials to help developers stay secure.

**No credentials were used or accessed** - this is pattern-based detection only.

---

*If this is a false positive, please close this issue. Thanks for keeping GitHub secure!*

**Bot:** Raccoon Key Scanner v1.0
**Scan ID:** 20260408041335

Start by inspecting llms.txt and confirming whether the detected pattern is an actual AWS Secret Access Key or a false positive. Review the repository history and the linked AWS and GitHub secret-scanning guidance before changing anything. Done means the credential is rotated if valid, removed from the file and history, and future credential files are covered by environment-variable guidance or .gitignore.

Written by the indexing model from the issue text.