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

Nobody has claimed this yet.

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

[](https://endoflife.ai/loopback)

```markdown
[](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](https://shields.io/badges/endpoint-badge), regenerated nightly from vendor lifecycle policies.

If it's useful, the copy-paste snippet for your stack is one click at [endoflife.ai/badge](https://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](https://dev.to/endoflifeai/one-badge-that-tells-your-users-when-your-dependencies-die-1gbj).)

Review the manually maintained supported-versions tables in README and SECURITY.md, then compare them with the proposed Shields.io endpoint badge snippet. Confirm where a badge would belong and whether the external endoflife.ai data is acceptable; done means the maintainers approve a specific documentation change or close the proposal.

Written by the indexing model from the issue text.