Offer: self-updating EOL badge for your supported-versions table

Hi — I noticed you maintain LoopBack’s own long-term support table by hand in your README and SECURITY.md. We run endoflife.ai (lifecycle data for 488 products, built on the endoflife.date community dataset — we're contributors) and publish free Shields.io endpoint badges that show live support status:

[![LoopBack EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Floopback.json)](https://endoflife.ai/loopback)

When a version reaches end of life, the badge updates itself — no README edits, no CI. There are per-version badges too (e.g. pin the minimum version you support, so the badge flips the day your floor goes EOL). No signup, no tracking, no API keys — they're static JSON endpoints in the Shields endpoint format, regenerated nightly from vendor lifecycle policies.

If it's useful, the copy-paste snippet for your stack is one click at endoflife.ai/badge; if not, feel free to close this — no hard feelings. Not affiliated with any of your dependencies; just trying to make EOL status visible where people actually look. (Background: why we built these.)

Revisa las tablas de versiones compatibles mantenidas manualmente en README y SECURITY.md y compáralas después con el fragmento de badge de endpoint de Shields.io propuesto. Confirma dónde debería colocarse un badge y si los datos externos de endoflife.ai son aceptables; el trabajo se considera terminado cuando los mantenedores aprueben un cambio específico en la documentación o cierren la propuesta.