Possible leaked API key in this repository

Hi — an automated scan found what looks like a live **Anthropic** API key committed to this repository at:

- path: `readme.md`
- file: https://github.com/arlyon/keyleash/blob/3331930ce426644bcc9c3de78dac1b60c2018935/readme.md
- vendor rule: `anthropic-api03`
- key fingerprint: `sk-ant-a...` (sha256[:8] = `a3da76f0`, length = 93)

The scanner did **not** validate the key against the vendor's API — validating someone else's credential would be unauthorized access. Please treat the key as compromised regardless:

1. **Rotate the key immediately** in the vendor's console. Even if you have already removed it from the latest commit, it remains valid in git history.
2. Purge the key from history (e.g. `git filter-repo`) and force-push.
3. Move secrets to environment variables or a secret manager; never commit `.env` or equivalent config with live credentials.

The vendor's security team has been notified separately where a contact is known.

This issue was opened by an automated responsible-disclosure tool. Apologies for the noise if it is a false positive — please close the issue and I will not re-open it for this `(repo, rule)` pair.

The report identifies readme.md and a suspected Anthropic API key at the linked commit. First inspect the indicated file and confirm the finding without attempting to validate the credential; treat it as compromised and rotate it in the vendor console. Done means removing the exposed secret from repository history and force-pushing, then ensuring secrets are kept out of committed files.

Written by the indexing model from the issue text.