Add security.txt for standardized vulnerability disclosure

[Copilot]

Implements RFC 9116 security.txt to publish security contact and ownership information at /.well-known/security.txt.

Changes

• Added apps/web/public/.well_known/security.txt with:
  • Contact: GitHub Security Advisories + security@base.org
  • Canonical URL: https://base.org/.well-known/security.txt
  • Policy reference using HEAD (branch-agnostic)
  • Expires: 2027-02-20 (1 year validity per RFC 9116)

Result

Security researchers can now discover standardized reporting channels at the conventional .well-known URI. Next.js serves the file statically from public/ without additional configuration.

Notes

• Expiration date requires renewal before February 2027
• Follows same pattern as existing walletconnect.txt in same directory

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• ethereum.org
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)
• fonts.googleapis.com
  • Triggering command: /opt/hostedtoolcache/node/24.13.0/x64/bin/node /opt/hostedtoolcache/node/24.13.0/x64/bin/node /home/REDACTED/work/base/base/apps/web/node_modules/next/dist/bin/next build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.